Corporate Data Maintenance

1. Activate the *INTERNAL method if you want to be able to send information in the sending company.

1. To be able to send anything, activate the desired files (choosing from the supported, preloaded ones). Important: The associating files per document have a predefined sequence for validation of data and mapping purposes.

Note: You may want to separate the data you are transferring between your different companies. (E.g., one receiving company may only receive Pricing information for items while another may only receive Unit information for items). You can set this up as follows:

2. Create a new DI document subtype by copying an existing. All associating files are copied. In Work with DI mapping definition, (on the Header view panel), create a new mapping definition for the new document subtypes by copying the applicable record for subtype 1. Activate the files that you want to send/receive.

1. Set up (or select) a template that includes the following panels:
• Basic data
• DI methods
• DI documents
2. Basic data panel:
• If the business partner’s nature of business is only to receive data from this sending company (and not process any transactions in DC1), set the Type field to 9 (= Sundry).
3. On the DI methods, All panel, drill down on the *Internal method and define the following on the GDMR0134 panel:
• Archive directory = This field is optional, but if you enter a directory name, the outgoing documents will be stored on the IFS in archive directory/OUT as a backup.
4. On the DI documents, All panel (GDMR0141), drill down on each applicable DI document that you want to send to this business partner and define the following:
• Set Send document to YES if the data for the document is allowed to be sent by the business partner.
• Send address = The address to where the information is sent.
• Send routine ID = The information stated here must match that which is entered in the Work with DI transfer routines. The system preloads CDMSND. When the DI transfer routine is activated, and the applicable run interval has been reached for the send routine ID, the system will look in the sending company for something to send.
• File/mail names out = Enter the name of the file that will be transferred to the receiver. See Example of outbound string below. The more variables you use, the more unique the name. If you do not complete this field, then the system will allocate a default name, which will not allow the user to be able to identify what data information is being sent. Make this a unique name for the following reasons:

To prevent files from being overridden. If data is sent several times/day and the file name is not unique, then the data will be overridden every time a new file is sent with the same name.

For the receiving company to be able to identify from whom the data is being sent and what type of data is being sent.

1. Activate the *INTERNAL method if you want to be able to receive information in the receiving company.

If you want to prohibit fields from being updated/overridden with sent data in the receiving company you can do the following:

1. Drill down to the file that contains the field you want to protect. Choose the Field option and “add” the applicable field. The following fields provide enhanced protection:
   • Local update only = If you set this field to YES, the applicable field can only be updated locally. You will never receive data into this field from a sending company.
   • Default value = This field is used when “New” records are added in the receiving company (i.e. the sending company sends a record that does not exist in the receiving company). You can enter the default value for this new record. Entry in this field is normally only allowed if the Local update only field is set to YES. However, if the CDMDEFV (CDM Default value) function is activated in the Function control file, entry in this field is also allowed if the Local update only field is set to NO (e.g., business partner creation from an external CRM system). If such is the case, the default value is only used if the transaction value is blank.
   • Protect = If you want to prohibit end users from maintaining this field in the Maintenance program, set this field to YES. This protection applies to those files that use template handling, (i.e. BPARTNER and ITEM), plus ACCOUNT and takes precedence over any protection that may already be assigned on the panel in the template.

1. Set up (or select) a template that includes the following panels:
   • Basic data
   • DI methods
   • DI documents
2. Basic data panel:
   • If the business partner’s nature of business is only to send data (and not process any transactions in DC1), set the Type field to 9 (= Sundry).
3. On the DI methods, All panel (GDMR0134), drill down on the *Internal method and define the following:
   • Archive directory = This field is optional, but if you enter a directory name, the incoming documents will be stored on the IFS in archive directory/IN as a backup.
4. On the DI documents, All (GDMR0141) panel, drill down on each applicable DI document that you want to receive from this business partner and define the following:
   • Set Receive document to YES if the data for the document is allowed to be received by the business partner.
   • Receive address = the address from where the documents are received (i.e. the Send address defined in the sending company).
   • Receive routine ID = the information you state here must match that which is entered in the Work with DI transfer routines program. The system preloads CDMRCV. If you are planning on receiving information at different times of the day (e.g., ITEM data once per hour and ACCOUNT data once per day), it is recommended that you define unique receive routine id’s. When the DI transfer routine is activated, and the applicable run interval has been reached for the receive routine id, then the system will look in the receiving company for something to receive.
   • File/mail names in = mandatory entry in receiving company. Enter the name of the file that will be picked up by the receiver. There are several ways to enter the inbound string, but it must match the string specified in the File/mail names out field on this panel in the sending company for the applicable document. See Example of inbound string below.

1. For DI document ITEM, create as many document subtypes as you need, by copying subtype 1. For example:
• Create subtype 2 for company B
• Create subtype 3 for company C
2. For the newly created subtype(s), drill down to Method link level and add a new method link (assigning the “supported” names *INTERNAL and *ASWXML).

1. For DI document ITEM, create the applicable Document subtypes by copying subtype 1.
• In company B, create subtype 2.
• In company C, create subtype 3.
2. For the newly created subtype(s), drill down to Method link level and add a new method link (assigning the “supported” names *INTERNAL and*ASWXML).

• For DI document ITEM, drill down to DI document subtype, File and then Field level
• Add the applicable field (e.g. Item group)
• For the added field, drill down to Selections and add the values.

Repeat the same instructions as outlined in the sending company.

Sending company

For the CMDSND routine, define/displays the following:

• Automatic start: Set to YES if you want the CDM Send transfer to be started automatically by the first user that logs on to DC1 in the applicable CDM company. If YES, data will be sent if there is anything in the send log according to the run interval. Alternatively, select the Start routine option to manually start the transfer. To end the transfer job, select the End routine option.
• Run interval: Enter, in seconds, how often the system should check for data to be transferred.
• Pgm to run before: Displays the preloaded program that is used to check the send log for any data that is ready to be sent.
• Transfer program: This program checks the transfer control file for anything to be sent. If data exists, it picks the data from the DI Interchange files, performs the mapping and places the information in the Send address on the IFS.

Receiving company

For the CMDRCV routine, define/displays the following:

• Automatic start: Set to YES if you want the CDM Receive to be started automatically by the first user that logs on to DC1 in the applicable CDM company. If YES, data will be received if there is anything in the receive log, according to the run interval. Alternatively, select the Start routine option to manually start the job. To end the transfer job, select the End routine option.
• Run interval: Enter, in seconds, how often the system should check for data to be received.
• Transfer program: This program checks the Receive address on the IFS for any data. If data exists, it performs the mapping.
• Pgm to run after: Displays the program that complements the data with any default values and then validates the data. If the data is correct it writes the data to the actual files. If there are any errors, it sends the erroneous data to the error log.

Common fields

• Admin program: Displays the preloaded administration program that should trigger the other transfer-related programs to start. This program will do the following:
  • trigger the program that is entered in the Pgm to run before field, (i.e. the program that checks the send log for data),
  • which in turn triggers the program that is entered in the Transfer program field (i.e. the program used to physically transfer the data and performs the mapping),
  • which in turn triggers the program that is entered in the Pgm to run after field (i.e. the program that validates the data, complementing with default values, and writes to the actual file if correct. Otherwise writes to the error log).
• Admin data queue: Displays the preloaded administration data queue which is used by the administration program.

1. Access Work with DI documents.
2. For the applicable DI document you want to send, drill down to DI document subtypes. Ensure that the Outbound field is set to YES for subtype 1.
3. For the file you want to activate, drill down to File level.
4. Select the Activate option for the applicable file. What you enter in the Send file(s) now field has different results:
• If you set this field to YES, the data in the file is activated for sending and all records in the file(s) that have YES in the Corporate snd field (in the sending company) will be sent to the business partners that are connected to the applicable document and subtype.
• If you set this field to NO, the file is activated for sending, but only future changes (record add, change of data, delete-marked records) in the file will be sent to the business partners that are connected to the applicable document and subtype.

1. Select the applicable record in the Business partner file or Item file and choose the Act CDM option. This does two things:
   • Initiates the actual sending of the record data to all applicable receiving business partners.
   • Sets the Corporate snd field to YES on the Basic data panel for the selected BPARTNER or ITEM record.

For ACCOUNT data, the record is automatically sent according the run interval if the Corporate snd flag is YES in the Account file for the account part.

1. Access Work with DI documents.
2. Drill down to DI document subtypes and then File level.
3. Select the Activate option for the applicable file.
4. For the Send file(s) now field:
   • If you set it to YES, the file for the DI document is activated for sending and all records in the file(s) will be sent to all receiving business partners that are connected to this TABLE DI document and subtype.
   • If you set it to NO, the file is activated for sending, but only future changes (adding and changing of record data) in the table itself will be sent to the receiving business partners that are connected to this TABLE DI document and subtype.

1. Access Work with DI documents.
2. For the applicable document, drill down to DI document subtypes and then File level.
3. Select the Inactivate option for the applicable file. Note: This will inactivate the sending of this file for all receivers that are connected to this DI document and subtype.

1. Select the applicable record in the Business partner file or Item file and choose the Inact CDM option. This does two things:
   • Suspends any future sending of the selected record data.
   • Sets the Corporate snd field to NO on the Basic data panel for the selected BPARTNER or ITEM record.

For ACCOUNT record data, do as follows:

1. If the Corporate snd field is OPTIONAL in the G/L control file, drill down on the applicable record in the Account file and set the equivalent field to NO.

1. Access Work with DI documents.
2. For the applicable DI document you want to receive, drill down to DI document subtypes. Ensure that the Inbound field is set to YES for subtype 1.
3. For the file you want to activate, drill down to File level.
4. Select the Activate option for the applicable file.

1. Select the record in question in the applicable file (Business partner, Item or Account file).
2. Manually set the Corporate rcv field to YES. Note: For ACCOUNT data, this field will automatically be YES if the account part is set to MANDATORY in the G/L control file.

1. Access Work with DI documents.
2. For the file you want to inactivate, drill down to DI document subtypes and then File level.
3. Select the Inactivate option for the applicable file. Note: This will stop the reception of any data for this file sent from all trading partners that are connected to the actual document/subtype in the Business partner file.

1. Select the record in question in the applicable file (Business partner, Item or Account file).
2. Manually set the Corporate rcv field to NO. Note: For ACCOUNT data, this field will automatically be NO if the account part is set to NOT ALLOWED in the G/L control file.