With the enhancement, you can:
• Maintain/supply your own customer fields in the headers and items of all purchasing documents except purchase requisitions
• Update your own customer-specific tables

You cannot:
• Change standard fields
• Change data that depends on the document header in the items
• Change data that depends on an item in the document header

Includes

You incorporate your customer fields for the document header in the INCLUDE CI_EKKODB (in table EKKO).
You incorporate your customer fields for the document item in the INCLUDE CI_EKPODB (in table EKPO).

Dynpro areas

If you use the enhancement, you must create and generate the following dynpros (even if the dynpros are not going to be used):
• SAPLXM06 0101 Subscreen header purchase order
• SAPLXM06 0201 Subscreen header outline agreement
• SAPLXM06 0301 Subscreen header RFQ
• SAPLXM06 0111 Subscreen item purchase order
• SAPLXM06 0211 Subscreen item outline agreement
• SAPLXM06 0311 Subscreen item RFQ

You must identify all dynpros as subscreens. It is not necessary that they contain fields, but it is essential that they exist in order that no program abend occurs.

Function exits

The dynpros are linked to the standard program via function modules.There are function modules that provide your subscreen with data (export) and function modules that fetch data from your subscreens (import).

• Header screens:
o EXIT_SAPMM06E_006 Export data to customer subscreen for header (PBO)
o EXIT_SAPMM06E_007 Export data to customer subscreen for header (PAI)
o EXIT_SAPMM06E_008 Import data from customer subscreen for header
• Item screens:
o EXIT_SAPMM06E_016 Export data to customer subscreen for item (PBO)
o EXIT_SAPMM06E_017 Export data to customer subscreen for item (PAI)
o EXIT_SAPMM06E_018 Import data from customer subscreen for item
You can set or supply your own data fields in the PBO function modules.
You receive the current (possibly changed viz a viz the PBO call) data of the standard program in the PAI function module.