You must set up the various components before you can get an IDoc out of or into the system. Two types of components build and support the SAP EDI process.
1.Components specifically designed for the ALE/EDI process (for example, the port definition, partner profiles, and process codes)·
2.Flexible cross−application technologies that are deployed in the EDI process and can be adapted
across multiple applications (for example, Message control and workflow).
The Configuration Settings
The various configuration settings for the EDI process are done in the IMG and in the area menu of the EDI system.
Implementation Guide: The various EDI customization settings (see Figure 6.1) are available under the following path in the IMG: Basis Components, Basis Services, IDoc Interface/Electronic Data Interchange.
Number Ranges for IDocs :
Transaction: OYSN
Path: EDI settings in the IMG, Create number ranges Every IDoc created in the system, inbound or outbound, is assigned a 16−digit number that uniquely identifies it in the system. The IDoc number range is already defined. You normally do not have to maintain this number range, but theoretically you could exhaust the number range and then have to reset it.
Be careful when resetting the number range. Make sure that old IDocs with the number range to
which you are resetting have been archived and deleted from the system. Otherwise, the system will not be able to create IDocs in the number range that has been initialized.
Global IDoc Interface Parameters
Transaction: WE46
Path: From the Area menu of EDI, choose Control, Partner profile, IDoc administration In transaction WE46, you assign values to the global variables used in the EDI process.
The settings you need to make for the global IDoc interface parameters are explained in the following list.
IDoc Administrator : This parameter group specifies the administrator for the IDoc interface at run time. The IDoc Administrator group consists of two parameters, named Recipient Type and Identification, which identify the individual(s) who will be responsible for the integrity of the overall IDoc interface.
You must enter the recipient type (for example, US for user ID, S for position, or O for organizational unit), along with the identification value.
For example, if the position with position number 12345678 is assigned as the administrator, the value of the parameter in the Recipient Type field will be S, and the value for the Identification field will be 12345678. If a user with user ID AN000001 is the administrator, the value of the parameter in the Recipient Type field will be US, and the Identification field will be AN000001. This parameter is used by the workflow system in either of the following situations.
1.A technical error occurs in the EDI interface layer, for example, an error in deleting an IDoc file after successfully creating an IDoc.
2. An application error occurs in processing an IDoc. In this case, workflow first attempts to send a notification to the ID specified in the partner profile. If the error is such that the partner profile cannot be read, notification is sent to the IDoc administrator.
Normally, these situations should not occur because the IDoc administrator has overall responsibility for the interface and cannot handle application−specific errors.
It's better to avoid a user ID as the IDoc Administrator. You should use more abstract object types, such as position, job, or organizational unit. This approach saves you the headache of changing the entry when the user leaves the company or changes jobs. Compared to users, organizational objects such as positions, jobs, and organizational units tend to be more stable.(59.1)
Related Posts
EDI sub system part one and Two
EDI inbound process overview
EDI subsystem architecture and mapping
Vendor balance in local currency report
No comments :
Post a Comment