Ansicht
Dokumentation

RGJVEDIX - EDI Outbound Basic Configuration for new Client/Company/Billing-Struc.

RGJVEDIX - EDI Outbound Basic Configuration for new Client/Company/Billing-Struc.

CL_GUI_FRONTEND_SERVICES - Frontend Services   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

Description

Basic Configuration for JV EDI Outbound Process

Precondition

Initial installation of Joint Venture software and configuration of company and billing structure parameters for the company being configured. Ensure that company region (USA / Canada / International) and processing level (partner / venture) are maintained correctly.

Output

Updates the following tables programatically:

  • JV partner function
  • JV application code
  • JV output types
  • JV message types
  • JV outbound process types
  • Company configuration
  • Billing levels
  • Segment components
  • Segment drivers
  • Invoice service codes
  • JIBE class codes
  • JIBE subclass codes
  • JIBE tubular codes (Canada only)
  • JIBE non-tubular codes (Canada only)
  • JIBE condition codes
  • Contact function codes
  • Communication codes

Execution

This program should normally only be executed once in any given environment. It's purpose is to set up the base configuration delivered with the system, which may be used as delivered or it may be tailored to further meet individual requirements.

The company that is being configured must already have been assigned a billing structure which will be used by default for the billing structure dependant configuration. The region code assigned to the company will dictate if the configuration will be specific to the USA, Canada or International processing.

Tables populated by this program are expected empty for the client / company / billing structure being configured. If any of the tables configured by this program, are already populated when the program is executed/re-executed, then these will be bypassed (only tables with no entries will be populated). You may however choose to override the existing configuration by clicking on "X" the relevant table's check-box. Extreme caution is recommended when using overrides.






SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 2535 Date: 20240601 Time: 055610     sap01-206 ( 47 ms )