VOE1 Translation between EDI categories and SD item categories VOE2 Table EDSC view. Customer link to sales area detail. VOE3 Table view EDPVW. Add partner types that will be transferred to the IDoc. VOE4 Table view EDPAR. Link external partner number with our internal number. OVAI
Create entries for each Vendor / Partner description combination. (Vendors must match sold-to Acct. at Cust., and Partner descriptions must match ship-to Partner descriptions.) This transaction updates table T661W. SAP uses this table to determine the schedule agreement sold-to partner.
Scheduling agreements
OVA9 Create entries for each sold-to customer for which you will receive EDI schedule releases. At implementation, the only field that needs to be maintained is "Check PO number," which causes SAP to make sure that the PO number sent on the release matches the PO number on the schedule agreement. This transaction updates table T663A. SAP will not post an EDI schedule release, if this record is missing. OVAJ If you would like SAP to post schedule requirements using discrete dates only, instead of weekly and/or monthly buckets, you can indicate the days of the week that you deliver to this customer. SAP will divide the customer's quantity for a week or month evenly into the days of the week specified by the distribution function code. This code must be sent in the DELINS IDoc in field E1EDP16-ETVTF.
MESSAGE CONTROL
NACE Links to all the message control transactions via the application area
Delivery
V/36
Maintain output determination for deliveries (Output determination procedures)V10000 (Header output) has condition type LAVA (usually with requirement 1 NB: Use V/84 – V7ALLE – SHAD for grouped ASNs. I.e. Group deliveries into shipments
VV21 Create output condition records for shipping. LAVA – WE (Partner function) - We must add each new partner with VV21 VL71 Reissue output for deliveries
Invoice
V/54 Maintain access sequence for billing documents VV31 Create condition records for billing documents. (RD00 – RE Billing party) VF31 Reissue output for billing documents
Order response
V/30 Sales document output types (BA00) V/48, V/32, V/43 Maintain access sequence for sales documents VV11 Create condition records for sales documents. (BA00 – SP Sold to party)
IDOC ADMINISTRATION
WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment. WE05 View Idocs WE60 IDoc type documentation tool WE20
Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing.
BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
IDOC DEVELOPMENT
BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations. WE19 EDI test tool. Use to test inbound Function module changes. WE31 Segment create WE30 Create IDoc extension type WE82 Link Release detail to Extension IDoc Type WE57 Assign function module to logical message and IDoc type
