cancel
Showing results for 
Search instead for 
Did you mean: 

Purchase Order Collaboration scenario - Not generating IDOC in ECC

Former Member
0 Kudos

Hi All,

I have done all the necessary config in ECC (Message determination and partner profiles) but when I save the PO, message type is automatically picked up in the PO but when I click processing log it says message E0045 - IDoc '' was created and forwarded for transmission ". IDOC number is not generated as a result I am not able to forward the PO to SNC. I have given program BUS2012_ICH_R3 and routine as SEND_PORDCR1 in my processing routine for message type. We are using SNC 7.0.

I also tried using both ORDERS.ORDERS05 and PORDCR1.PORDCR102 as message type/basic types in my outbound parameters for partner profile but both dont work. I understand PORDCR1 is for the subcontracting scenario.

Please let me know what I should do so that I can generate the IDOC on the ECC side?

Thanks,

AK

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Nikhil,

I tried the same settings you had mentioned and I am still getting the message "IDOC " " has been transmitted".

When I gave RSNASTED program and EDI_PROCESSING as routine, it gave me an error message stating that the key APOCLNT800/LS/LS/EF/ZSNC is not there in table EDP12. But I checked this table and this combination is maintained there. When I changed the program to BUS2012_ICH_R3 under special function medium (8) and form as SEND_PORDCR1, it didn't give me any error but the IDOC was " " and it didn't generate any IDOC.

This is what I have done thus far.

Output types - ZSNC - program BUS2012_ICH_R3 and routine SEND_PORDCR1.

Condition records created for Porg/Vendor/doc type with medium 8 LS and partner APOCLNT800

In Partner profile under LS and partner number APOCLNT800, I have created message type ORDERS with basic type ORDERS05 and checked transfer immediately with packet size 1. Then in the next tab, I have selected EF application, ZSNC as message type and process code as ME10. I didn't click the change indicator. Still no luck in moving forward. Should I create something under LI for this vendor? I have tried other combinations, but nothing is working. Should I activate any model for this to work?

Your help has always is appreciated.

Regards,

AK

Former Member
0 Kudos

Ashvin -

Did you ever get resolution to this issue?  We are trying to install SNC and we are having the exact same issue in our ECC system.  I'd appreciate any assistance you can provide.

Thank you,

Jeanne

Former Member
0 Kudos

Hi Jeanne,

No I did not receive an answer looking at my notes.

Former Member
0 Kudos

Ashvin

Are you using standard "NEU" output type or custom output types ? I just setup the SNC the POs are flowing smooth. Also usually your EDI processing should be immediate to generate the docs for vendor settings. Please give more details so that i can recommend any solutions? Exact steps what you have configured in the system and where you deviate from standard SAP output types.

Thanks

Srini

Former Member
0 Kudos

I thought I'd share this in hopes of helping anyone else that might end up with this issue.  The way we fixed this was to specify the BAPI in BD64:

Here is where you create a model view for sending the message types to the target system.  Program BUS2012_ICH_R3 is hardcoded with these values 'BUS2012' & 'CreateFromData1' So you map this one with a BAPI, not a message type.

BD64 click add BAPI and fill in the following:

Object type          BUS2012

Method               CREATEFROMDATA1

Then save.

Hopefully this helps someone!

Jeanne

Former Member
0 Kudos

Hi Jeanne,

I'd like to consult you for a question. Hope you can help me.

We received the ASN information from SNC and did goods receipt successfully. But there is a scenario that we have to return some of the goods through migo-102 because of the quality or some other reasons.

If there is a message type could send an IDOC to SNC to update the information of goods receipt? Then the vendor could continue to make an extra ASN to replenish.


Thanks and Regards

Freesen Yue

peter_wallner2
Active Contributor
0 Kudos

Hi Jeanne,

Thank you - your post just solved a problem on my side.

Best regards,

Peter

Former Member
0 Kudos

Sorry for not responding sooner.  I didn't see that you had commented.  We use the DESADV IDoc to update the goods receipt quantity; however, we need to manually delete the ASN in both SAP and SNC before a new one can be transmitted.

I hope this helps.

Former Member
0 Kudos

Thanks for your reply.

But how do you delete the ASN in both SAP and SNC?

Besides, If I didn't return all the goods receipted about the ASN, I don't think the ASN should be deleted directly.

Former Member
0 Kudos

You can cancel the ASN in SAP by deleting the inbound delivery (VL09 to reverse goods receipt, VL32N to delete inbound).  Prior to receipt, the ASN can be cancelled in SNC on the ASN Details screen and clicking the 'Cancel ASN' button.  After receipt, you need to select the 'Reset GR status' to reverse the status from 'GR Complete' to 'Published'.  Then select the 'Cancel ASN' button.  You can then run transaction /n/sca/dlv_del to delete the ASN from the database.  This is NOT recommended if you are not wanting to completely eliminate the ASN as if it was never sent.  We only do this when suppliers send them in error (we don't have the ability to automatically change or cancel ASNs set up in the system yet - we had thought there would be no need for this).

If you are returning some of the goods, I would not recommend cancelling the ASN as they truly shipped the product.  Instead, a return PO should be created in SAP.  Standard SNC functionality does not support this.  We had to make custom modifications to handle it within SNC, but you could process these outside of SNC.

Former Member
0 Kudos

Hello Ak,

In your output type maintain program =RSNASTED and Form Routine=EDI_PROCESSING.

Also in your partner profile maintain data as below:

Message type=ORDERS

receiver port=<PI_PORT>which connects to your PI system

Pack size=1

Check the radio button transfer IDoc.Immed.

Ouput Mode=2

Basic Type=ORDERS05

Checked Cancel Processing After Syntax Error

In message control tab:

Maintain application:EF,Message type=<Your output type>,Process code=ME10

save the above setting and try.

Regards,

Nikhil