Related topics
This panel displays all of the companies that have been validated as Multi Distribution Centres (MDC). DC1 Multi Distribution Centre enables all of the companies that are validated here to exchange sales order, purchase order and invoicing information via the DI (data interchange file).
Note: In order for information to be exchanged via the DI file, the companies that are defined here must be using the DC1 system. These companies must, in return, validate your active company in their DC1 system’s MDC company control file.
Each MDC company must be defined as being of an internal (within the same DC1 system) or external (within another DC1 system) type. From this panel the necessary parameters for establishing a communications link, between the two companies that use the MDC functionality, is defined.
This company level information is later retrieved by the customers and suppliers, that have been defined as MDC types in the Business partner file, in order for the communication link to be established between them.
Options
Selection fields
- Company
- This column lists the MDC company codes.
- Name
- This column lists the MDC company names.
- Internal
- Indicates if the company is the internal company (i.e. existing within the same DC1 system as your active company).
- External
- Indicates that if the company is external (i.e. existing within another DC1 system).
- Remote company
- This field is currently not in use.
- Data file library
- This column lists the libraries which the companies use to store the data queues.
- Remote location
- This field is currently not in use.
- Virtual controller
- This field is currently not in use.
- Local location
- This field is currently not in use.
- Remote mode
- This field is currently not in use.
- Remote network ID
- This field is currently not in use.
- Send int request
- This column lists the data queue used when sending interactive requests to this company. The data queue will be read in one of the company’s MDC direct jobs. The name of the data queue is automatically built by the system.
- Send answer
- This column lists the data queue used when sending answers to this company. The data queue will be read in one of the company’s MDC direct jobs. The name of the data queue is automatically built by the system.
- Send batch transfer
- This column lists the data queue used when sending a batch transfer of data to this company. The data queue will be read in one of the company’s MDC direct jobs. The name of the data queue is automatically built by the system.
- Wait seconds
- This column lists the number of seconds the current system will wait for a reply from the related company. If an answer has not arrived within this allotted time, the company’s MDC direct job will be considered inactive and no communication will be established.
- Automatic matching
- Indicates if the supplying company should create invoice (SROLBA), VAT transaction (SROLBV) and invoice line (SROLBAL) interface files in the demanding company in order to automatically match invoice lines to purchase order lines.
Work with MDC company control file (ASGD14004)
On this panel communication parameters set up in this file for the MDC companies are later retrieved by MDC suppliers and MDC customers and used to exchange sales order, purchase order and invoicing information.
- Company
- Enter the company code which will identify the MDC company you are adding. Note: If this is an internal company (i.e. existing within the same DC1 system) the company code defined here cannot be the same as the company code assigned to your active company in Work with companies.
- Name
- Enter the name of the company.
- Release
- This field is applicable if you plan on communicating between two DC1 companies with different release (PTF) levels.
MDC has been “prepared” to handle companies with different PTF levels. All communication between two Enterprise companies within MDC is handled by unique transactions sent through data queues. The PTF levels supported in standard include:Demanding company Supplying company 500E 800A 550L 800A 600I 800A 800A 500E 800A 600I Enter the release (PTF level) of the MDC company. The MDC transaction mapping control file holds information regarding all transactions whose layout has been changed and is not identical for two different PTF levels. The result is as follows:
- When an MDC transaction is to be sent and different PTF levels have been defined for the two companies in this MDC company control file, a check is made against the mapping file to see if a record exists for the transaction number and from-to PTF level.
- If a record is found, a new mapping program (defined in the mapping record) is called before the transaction is sent. This mapping program will adjust the differences for the transaction. The adjustment can be to initiate a new value that the receiving company expects to get or to not send certain information if that has been removed in the receiving company’s transaction layout.
- When the mapping has been done, the transaction is sent according to the layout defined for the receiving company’s PTF level.
- If no record is found in the mapping control file, even though different PTF levels have been defined in this MDC company control file, then the layout of that particular transaction has not been changed and can be sent without any extra mapping.
- If no PTF levels are defined in MDC company control file, it is assumed that the two companies have the same PTF level and no mapping at all is needed.
If the PTF level does not support the actual transaction, then the transaction is not sent. See the MDC between different Enterprise releases technical reference for more information.
- Internal
- Indicate if this is an internal company (i.e. existing within the same DC1 system as your active company). Note: If you set this field to YES, the External field must be set to NO and the code in theCompany field must not be the same as the company code assigned to your active company in Work with companies.
- External
- Indicate if the company is external (i.e. existing within another DC1 system). Note: If you set this field to YES, the Internal field must be set to NO.
- Current comp release
- This field is applicable if you plan on communicating between two DC1 companies with different Release (PTF) levels. Enter the Release/PTF level of the current company.
- Automatic matching
- Indicate if the supplying company should create invoice (SROLBA), VAT transaction (SROLBV) and invoice line (SROLBAL) interface files in the demanding company in order to automatically match invoice lines to purchase order lines. If you set this field to NO, then only the invoice interface file will be created and the invoice matching needs to be performed manually.
Data queues
The fields below display the data queues used when transferring information to the company that you are currently defining.
- Send int request
- Displays the name of the data queue used when sending interactive requests to this company. The data queue will be read in one of the company’s MDC direct jobs. The name of the data queue is automatically built by the system.
- Send batch transfer
- Displays the name of the data queue used when sending a batch transfer of data to this company. The data queue will be read in one of the company’s MDC direct jobs. The name of the data queue is automatically built by the system.
- Send answer
- Displays the name of the data queue used when sending answers to this company. The data queue will be read in one of the company’s MDC direct jobs. The name of the data queue is automatically built by the system.
- Data file library
- Enter the name of the library which the company uses to store the data queues. The library name must not be the same as the your active company’s file library.
- Wait seconds
- Enter the number of seconds your current system will wait for a reply from this company. If an answer has not arrived within this allotted time, the company’s MDC direct job will be considered inactive and no communication will be established.