Stratergy for IDocs

pts.
Tags:
Development
SAP
Upgrades
The following are the three sources of sales orders in the current scenario for the client. 1. IVR orders from the IVR system ( Phone lines ). - The files are not in a standard IDOC format. - Does not require a order confirmation. 2. Offline order entry software ( OOE). - The files are not in a standard IDOC format. - Requires a order confrimation. The confirmation needs to be in a specific format for the recieving system to interpret and is different from the IDOC outbound confirmations. 3. EDI orders. - IDOC format. Will move directly into the system. Stored under ( /usr/orders/ ). - Requires a order confirmation. One of the stratergies I had in mind for doing this is as follows :- 2 backgroud jobs. Inverval 2 minutes. Job 1. A different user id to qualify the source of the incoming order. To trace down the orders created by OOE to set a outbound confirmation. - Step 1. Process the OOE files and convert to IDOC format and move it to a common folder say ( /usr/orders/ ) Job 2. ( User id : jobadmin) - Step 1. Process the IVR files and convert to IDOC format and move it to the common folder ( /usr/orders/ ). - Step 2. Process all the files in the /usr/folders/ by calling EDI_DATA_INCOMING. Please let me know your suggestions on this. Also the following are some issues I am not sure of. 1. Outbound confirmation for OOE ? How do we trigger this only for orders recieved from OOE. 2. Error handling. Stratergy on moving the files to processed or error folders depending upon IDOC creation.

Answer Wiki

Thanks. We'll let you know when a new response is added.

Not knowing all of your requirements, it seems to me you have a infinite number of choices. But I can offer a few suggestions:
- when you talk of order confirmations, I would recommend that you send the confirmation from inside of SAP from the sales order itself via output determination. You can configure different output types to handle the different formats. You may need a small piece of code in a requirement routine to control which outputs get sent…depends on your sales order design.
- I would recommend having sales order data in SAP different for each scenario, for easy separation/reporting. I would think you would want to be able to list all sales order types, for example ‘list all OOE sales order numbers from yesterday’. You could use a different ordertype for the sales orders. If you want the IDOCs to be separated, you can use different message functions/message codes.
Good luck.

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Solutions1
    Are you dealing with a trickle of orders? Or with hundreds per hour - enough to create queueing issues? Do the external order-taking systems have enough edits and SAP master data to get customer accounts right, pricing, etc? The ugly possibilities are dropped orders and rejected orders, so what you implement needs to minimize both. Also, you should create a unified console function and supporting database so that some person or group can quickly review the flow (e.g., so that if someone asks what happened to IVR transaction 12345 it is easy to figure out whether and when it passed through your job steps). If an order is somehow lost or shipped late, your translation processes will be high on the list of the "usual suspects."
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following