EDI PO Acknowledgement

Hi All,
I created a Purchase Order , Now when i am trying to create a PO Acknowledgement i am getting an error with the status 60-Idoc segment syntax error in ( IDoc segment is not identified) WE31 status set to released already .
stilll its not identifiying the segments . which are mandatory for the PO Acknowledgement .How to find out could you please help me out in this .
Thanks & Reggards,
Balakrishna Vegi.

Dear Balakrishna,
I am not very familiar with PO ack. for MM. is this message type 855?
The error you have mentioned normally comes if the syntax of the idoc is not as per the EDI standard.
have you extended the standard message type?
Thanks.

Similar Messages

Inbound 855 EDI PO Acknowledgement Transaction

We are trying to take an 855 EDI PO Acknowledgement Transaction, and have the price on the PO and the delivery date on the PO automatically change.
When we process the IDoc for the 855 EDI PO acknowledgement, we can see that the new delivery date is put on another field on the PO (instead if chaning the delivery date on the PO line item). Also, we cannot get the price to change.
Has anyone been successful to change the PO price and delivery date when processing the inbound IDoc for the 855 EDI PO Acknowledgement transaction?

Hi Bonnie,
I'm not sure if you solved this one yet, but here are a few ideas.
The IDoc would be an ORDRSP message type. The quantity and date would be in e1edp20-wmeng and e1edp20-edatu. When the IDoc is processed it will not change the delivery dates on the PO, it will be entered on the PO as a confirmation for that quantity and date. So if you have a PO for quantity 10, there could be two e1edp20 segments on the IDoc, one for a quantity of 6 on one date and one for a quantity of 4 on another date. For this IDoc you would get two confirmation lines on the confirmations tab in the item detail on the PO. These lines are in the ekes table. They are stored as AB confirmations. There are also LA confirmations on this same tab and same table that come from the 856 advance ship notification.
The price would be brought in the e1edp01 segment in the vprei (price) and peinh (per) fields for per unit pricing or in the netwr field if it is an extended value. The vprei/peinh is put in the EDI1 condition field on the PO and the netwr is put in the EDI2 condition field. For this to work, you have to have those two conditions in your PO price procedure. You also have to have the confirmation control key configured to accept the price.
The function module used for all of this is IDOC_INPUT_ORDRSP.
We are in the midst of getting this implemented and have had to redo a lot of our processes centered around the po delivery date. This has been very painful for us, but we hope it pays off in the long run. Our previous process was to use a custom function module that would call a BDC (now we would use the BAPI_CHANGE_PO) that would directly change the delivery dates (eket table).
Hope this helps. Let me know if you have more questions and I'll try to help.
Jack Schmitz
Border States Electric

Adapter Modules & split 997 channel reqd for splitting Edi and Acknowledgement

Hi,
I am using PI 7.11 with B2B add-on installed.We will be using AS2 adapters ,as of now
configured file adapters in place of it.
This B2B scenario does not consists of Party because 1 sender and 1 receiver system is involved as of now.
May be client provides identifiers details and include party.
In my previous B2B scenario(PI 7.3) involving Seeburger , AS2 channel was configured with(image shown below)
SeeClassifier,BIC, message splitter modules and Split997 channel for splitting EDI PO and Functional Acknowledgement.
What are the adapter modules that will be required in case of B2B add on (PI 7.11)and does it requires
EDI separator channel for splitting EDI doc & Func Ack.What can be the other probable issues.
How we will monitor the messages and Ack once its implemented end to end?
Regards,
Mayank Yadav

Hey Mayank,
Inbound Scenario configuration: (3 step)
1) Sender AS2 (EDI messages) -----> EDI separator receiver (no mapping required here; EDI separator is used to split bulk EDI messages and configure acknowledgements (997) if required)
2) EDI separator sender (with message type(eg.850),version and sender ID/receiver ID configuration; here X12convertor module is used to change raw edi into XML) ----> Idoc or any receiver channel (inbound)(here you have your actual mapping)
(if 997 is configured as requested in the first step; then you need to handle the 997 generated by EDI separator)
3) EDI separator sender (997 message type,version,reverse combination of sender ID,receiver ID) to Receiver AS2 ( no modules required pass through)
Outbound Scenario configuration
1) sender channel (say Idoc) to AS2 receiver (requires mapping)
997 file can be sent back by partners (EDI 997 as acknowledgement)
this will be taken care like any other inbound message) which can be then converted to SYSTAT IDOC or so to track the status of outbound message.
B2B status tab in PI monitoring helps you track acknowledgements
Hope this answers your question:
What are the adapter modules that will be required in case of B2B add on (PI 7.11)and does it require
EDI separator channel for splitting EDI doc & Func Ack.What can be the other probable issues.
How we will monitor the messages and Ack once its implemented end to end?
For detailed information on this; please refer Functional Acknowledgement (Inbound and Outbound FA 997)- for Beginners
Regards,
Pooja

SAP EDI order acknowledgement

I am having trouble sending out certain 855 (Edi acknowledgements).
The issue is that certain CRLF carriage return line feeds are getting translated to a # in the IDOC......
I am not sure how it can happen...............
Can anyone provide possible reasons??? what the cause could be???
I need to know the why before we can discuss fixing it......................

Oh, sorry about that. Wow. OK, let me re-word this: "ur not providing enough info 4 anyone to help u" and "ur asking in a wrong forum".
Refer to this link:
http://scn.sap.com/community/getting-started/blog/2010/05/12/asking-good-questions-in-the-forums-to-get-good-answers

Intercompany sales without the EDI piece?

Hi all,
I am looking into setting up and intercompany sales process for my client. It is a straightforward process whereby product will be sold out of one company code (A), and delivered out of a plant that is in another company code (B). I have already configured the intercompany invoice to be created from the company code B vendor to the selling company code, A, and this is working great. My question is... do I need to configure the EDI piece to create the invoice receipt within company code A? I seem to remember at a previous client that we did intercompany sales without this piece, but I wasn't close enough to it to remember the details. Any thoughts/comments would be greatly appreciated.

Hi Barry,
If you guys are using EDI for acknowledging the reciepts of STO, sending ASN's etc. then I would say to set up the EDI for the invoice as well, if not forget about it.
It should not impact your outcome.
We do not use EDI for the Intercompany operations.
Mostly Confirmations through Email.
Thanks
Murtuza

Adapter Metadata

Dear all.....
We are developing a custom adapter to handle EDI 997 acknowledgement file.I would like to know what configurations should be done in Adapter Metadata.....
Helpful answers will be given reward points.........
Regards,
Azahar

Dear Jalaludin,
With adapter metadata you can define configuration data needed for a certain type of adapter at design time. Adapter metadata define the part of a communication channel that is specific to the adapter type.
The functions for creating and editing adapter metadata are intended for parties developing new adapters. They are not intended for general use.
For more information about adapter development, see Adapter and Module Development.
You can export adapter metadata as an XML file and import it into the Integration Directory. In this way you can provide the configuration with new adapter types.
To export adapter metadata, choose Adapter Metadata ® Export XML Description in the object menu bar.
SAP ships adapter metadata for all the adapter types it provides. You can find the adapter metadata shipped by SAP in software component SAP BASIS, software component version SAP BASIS 6.40, in namespace http://sap.com/xi/XI/System.
You can find adapter metadata in the corresponding namespace in the navigation tree of the Integration Builder (Integration Repository) under Adapter Objects ® Adapter Metadata.
For more details see the below link
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm

Difference between VMI and collaboration with customer

Hai,
I am trying to understand the difference between VMI and collaborative planning with customer(CPC)
Please correct me if I am wrong. In VMI, a vendor or manufacturer sells his material to customer and through EDI, the customer gives the information such as forecast, stock etc.
In CPC, the vendor and customer interchange information, such as demand, stock levels, promotions, delivery dates etc., based on ITS.
What is the difference between these two?
If I am not wrong, EDI is used for outside company communication andITS for within. So, can I say that VMI is for customer outside the company and CPC for internal customer?
Thank you.

Hi Visu,
Service provided by a vendor for a customer, whereby the vendor plans material requirements in the customer's company. Vendor-managed inventory is only possible if the vendor has access to the customer's current stock and sales data.
In the ERP system, the following functions are available for vendor-managed inventory:
Transfer of stock and sales data by EDI
Receipt of stock and sales data by EDI
Replenishment planning for customers
Creation of a purchase order for an external EDI order acknowledgment
supply chain management tool that synchronizes demand signals and supply chain activities by utilizing Internet technology. Collaborative Planning enables supply chain partners to view, share and synchronize common information within the supply chain.
Hope this helps.
Regards,
Mohan

Acknowledgement of Idoc of EDI type

Hi all,
We have the following scenario :
R/3 > Idoc (asynchronous) > PI BPM > Http (Synchrnous) > B2B Partner (EDI Customer (ALE KU))
We want to acknowledge our idocs using a node of the XML contained in HTTP response.
It seems we can't use ALEAUD to do that because our target isn't a logical system (EDI communication)
Is there a way ???
Thanks a lot.
J.C.

Thanks Barry,
Yes we have a response message with a node that contains a code allowing us to know whether it is ok or not !!!
But we don't know what message to build (Which idoc) ?
For the moment we use the stanbard acknowledgement procedure in BPM (send step of type acknowledgement : positive or negative)
But generated ack has the following error in SXMB_MONI :
SAP:Stack>Unable to convert the sender service BPM_CchubwooInvoice to an ALE logical system</SAP:Stack>
I think BPM try to send an ALEAUD idoc but it is not adapted to EDI partners ....

EDI 997 - Functional acknowledgement

Hi,
Our requirement is to send and recieve functional acknowledgement through EDI.
What is functional Acknowledgement?
Can any one help me out in using functional acknowledgement?What is the message type and functional modules involved for processing functional acknowledgement.Once I recieve a funtional acknowledgement where should that data be updated?
Any help in this regard would be appreciated.
Regards,
Nagaraju Donikena.

Swapnil Bachal thanks for your help.This would be helpful when I recieve functional acknowledgement from my vendor.
Now my other requirement is that when ever I recieve a purchase order from my vendor I need to send 997 and also create the sales order for the PO recieved.I understand that for any inbound idoc I can configure process code which is attached to some Function module.SAP has provided with a standard function module which would create a sales order for the PO recieved.Could you please advice on how to send the 997 simultaneously.
Regards ,
Nagaraju Donikena.

EDI 860 PO Change and 865 PO Change Acknowledgement

Currenlty we handle our EDI 860 PO Changes not via the ORDCHG Message Type but rather we send the change via email and the users manually change the order. This was done because the users did not want SAP to automatically update the order. Now we have a mandatate by a customer to do the 865 PO Change Acknowledgment. Can anyone tell me if there is a standard way to do the 860 and 865 in SAP, without having the 860 ORDCHG automatically update the order? Any help would be great.
Thank You
Dave Ackerman

Is that the only difference in the EDI mapping for 850 PO change compared to 850 PO?
I still don't understand how the system will know which sales order corresponds to the incoming PO change. In the TCode VA02, we have to input the Sales Order # in order to change the sales order. How would the system know how to do this when a PO change is sent through EDI?

Order acknowledgement inbound scenario in EDI

Hi,
We have to setup the order acknowledgement inbound scenario in EDI. as I am new to EDI need help in this. If somebody has any document or link of tutorial please send it to ankur.ty5 @ gmail.com .
Thanks in advance
Ankur

same here, need docs ..Please send'em to xterm2121 @ gmail com

Send an automatic acknowledge EDI 855

Hi there, Im working in an Idoc integration and EDI using Inovis as middleware, actually Im receiving ORDERS05 Idoc from Inovis to create a Sales Order, I need to trigger an action at the moment when Sales Order is created in SAP, to send an automatic acknowledge that would be mapped to EDI 855. I would like to know how I can trigger this action in SAP.
Thanks in advance.

Hi Alexis,
to get this configuration working set up
ORDRSP message
with message control (we20) entry V1 BA00 SD10
for such IDOC scensario with screenshot examples check out my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
you can also check this doc for sales order output (BA00):
http://help.sap.com/bp_retailv1470/documentation/EN/Merchandise%20Distribution_EN_CUST_V147.doc
is that what you're looing for?
Regards,
michal

997 Acknowledgement Timeout Settinsg - X12 EDI

Hi,
In Covast, there is an option setup for timeout period on functional and technical acknowledgements. Can we setup same on BizTalk Server 2013? How would system know that the particular interchange did not receive the 997s in predefined time?
For example, if I don't receive 997s within 72 hours, I want to have a report of those interchanges.
Any help on putting me in right direction will be appreciated.
Thanks

EDI Status Reporting is what you would use for this:
http://msdn.microsoft.com/en-us/library/bb226463.aspx

Delivered workflow name for EDI PO order acknowledgements

Does anyone know the workflow that is delivered for the PO order acknowledgements? Right now, if an IDoc (basic type ORDERS01 for Message type ORDRDP) comes into our SAP system, if the IDoc has an error because of a u/m problem price change, or quantity, the IDoc goes into a '51' status but it does not get routed to the user ID on the WE20 set-up (it is not in my SBWP SAP Inbox)

You have to create the custom object type to push the filed PO to the use inbox based on the Idoc.

Rejecting functional acknowledgement before reaching PI. (incoming EDI)

Hi Friends,
Scenario is EDI (X12 format)<-> PI <-> IDOC (Shipment notification)
Requirement is we need to send reject acks (997) if the sending X12 doesn't have item details.
This has to be accomplished at Seeburger level and should not reach PI. (bcause if it reaches PI then sender (EDI) assumes that we already picked up the file using the splitter adapter)
Any inputs is grtly appreciated.
Regards,
Pavan

Solved,
We are making changes in the BIC mappings in Seeburger.

EDI PO Acknowledgement

Similar Messages

Maybe you are looking for