Shared Top Border

Enterprise Resource
Planning Portal

 

Advertise | Founder BLOG

ERPGenie.COM ABAP Tips and Tricks Database

THE ultimate
ERP website

 

Forums | Vote for us |

Google    Other Search Options

Login

Login to view more content!!!





Lost Password?
No account yet? Register

Main Menu

Home
Search
What's New
Sample Code
Tips and Tricks
Utilities
Downloads
Site Map
Feedback

ABAP Resources

Publications
Latest Job Postings
Submit Resume
ABAP Books
ABAP Training
News
Events
Forums

Registered Access

Poll

What area of ABAP are you interested in?
 

Last 5 Contributions

5 Most Popular Contributions

Home arrow Tips and Tricks arrow User Exits arrow Adding a new field to the PO Comms Structure
Adding a new field to the PO Comms Structure PDF Print E-mail
User Rating: / 0
PoorBest 
Written by Kevin Wilson   
Wednesday, 11 July 2007
Need to add a new field to the PO communication structure in order to use it in your output determination?
The communication structure to be maintained can be taken from table T681Z.
Table T681Z can be displayed with Transaction SE16.
Use 'B' for message determination and application EF for purchase order.
The structure for purchase order communication is KOMKBEA.
 
Procedure:
1. Include field ZZ<field> in the communication structure KOMKBEA.
 In this structure there is an include that is provided for additional fields.
 In this Include KOMKBZ you must include the field with the name ZZ<field>.
2. The same field must also be included in structure KOMB in Include KOMBZ (the same procedure as under point 1).
3. In table T681F use Transaction SM31 with key B, EF to add the same field.
 As of Release 4. 0 you can use view V_T681F in Transaction SM30 for that purpose.
 Enter usage 'B', your application and field group '001'.
4. In the message determination, the system runs perform USEREXIT_KOMKBEA_FILL. This perform is in program RVCOMFZZ.
The source code should be changed as follows:
FORM_USEREXIT_KOMKBEA_FILL.
  COM_KBEA-ZZ<feild> = <field-value>.
ENDFORM.
Any EKKO field with the following syntax can be used.
COM_KBEA-ZZFIELD1 = COM_EKKO-field.
5. After making this change, you must create a new condition table and an access sequence that contains the new field.
 If a new access sequence and condition table have already been created before changing the communication structure, this must now be deleted again.
 Points 1 to 5 must be carried out in sequence.
6. Note that the syntax check in Include RVCOMFZZ can deliver errors.
 Check the entire function group (according to Note 2152).

Related Items:
 
< Prev   Next >
[ Back ]

Google Search

WEB
ERPGenie.COM
EDIGenie.COM
WorkflowGenie.COM

Statistics

Contribution Activity
Utilities: 38
Tips and Tricks: 334
Sample Code: 166
Total Contributions: 553

Member Activity
Members: 6305 since 2/1/2007!
New: 0 since yesterday!
Visitors: 1167754
We have 1 guest online

Newest Members

Welcome our newest members:

Google Ads

Shared Bottom Border

Contact Us | Polls | Add URL | Contribute | Privacy | Terms | Feedback

Discussion Forum | BLOG | Consultants: Post your resume | Companies: Advertise on ERPGenie.COM | Post Job
Financials Consultant | Consultant Review | Gallia Consulting | Supply Chain Project | SAP Financials Forum
GenieHoldings.COM, Inc. | Genie Press | WorkflowGenie | ESAGenie | ERPTopSites | ABAP Tips and Tricks | SAP Solutions Database
EDIGenie | Searching Survivor

©2001-2008 Genieholdings.COM, Inc. All rights reserved. ERPGenie.COM, EDIGenie.COM, WorkflowGenie.COM and ESAGenie.COM are Trademarks of Genieholdings.COM, Inc.

All product names are trademarks of their respective companies. GenieHoldings.COM, Inc. and it's websites are in no way affiliated with SAP AG.
 SAP, SAP R/3, R/3 software, mySAP, ABAP, BAPI, xApps, SAP NetWeaver, and and any other SAP trademarks are registered trademarks of SAP AG in Germany and in several other countries.
 Every effort is made to ensure content integrity. Use information on this site at your own risk.