Scribd Logo
Upload

Welcome to Scribd!

  • Analysis - Shipment Not Created

    Uploaded by

    moumitasid
    4 views5 pages
    The document discusses two purchase order cases where shipments were not automatically posted after inbound deliveries were created. For the first case, no inbound IDOC was received from the B2B Hub system for purchase order 3563318618, so the shipment had to be manually processed. For the second case, an error occurred during processing of the inbound IDOC for purchase order 3563211402, preventing the shipment from being posted automatically. A similar order where the IDOC processed without errors resulted in automatic shipment posting.

    Original Description:

    Original Title

    Analysis_Shipment Not Created

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document discusses two purchase order cases where shipments were not automatically posted after inbound deliveries were created. For the first case, no inbound IDOC was received from the B2B Hub system for purchase order 3563318618, so the shipment had to be manually processed. For the second case, an error occurred during processing of the inbound IDOC for purchase order 3563211402, preventing the shipment from being posted automatically. A similar order where the IDOC processed without errors resulted in automatic shipment posting.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    4 views5 pages

    Analysis - Shipment Not Created

    Uploaded by

    moumitasid
    The document discusses two purchase order cases where shipments were not automatically posted after inbound deliveries were created. For the first case, no inbound IDOC was received from the B2B Hub system for purchase order 3563318618, so the shipment had to be manually processed. For the second case, an error occurred during processing of the inbound IDOC for purchase order 3563211402, preventing the shipment from being posted automatically. A similar order where the IDOC processed without errors resulted in automatic shipment posting.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 5

    For the first reported failure case:

    PO:3563318618

    After comparing with recent success case in EWP where shipment is posted:

    PO:3563370315
    Shipment:2009744775

    It is observed that after inbound delivery creation through RFC_CIG, shipment is posted through
    Inbound IDOC.
    The inbound IDOC was received from B2B Hub system.

    For Reported failure case:

    The reported inbound delivery was created manually. I tried to find why was it not created through
    IDOC in similar way as success case but couldn’t find any idoc ,that means B2B didn’t seem to have
    sent any data for this.

    PO: 3563318618
    As there was no data from B2B received into SAP, so shipment was not automatically posted.
    This needs to be checked in the B2B Hub system.

    Also, as this delivery was created manually the rest of the shipment process will have to be done
    manually.

    __________________________________________________________________________________
    For second reported failure case:

    PO: 3563211402

    There was Inbound IDOC error status during USBATCH processing of the inbound delivery, which did
    not allow the shipment to be posted. After which the IDOC was sent into status 68 by user
    XFQ1674(Kelliann.hansel@es3.com) to stop further processing the error.

    Due to the error: No Vendor with SCAC code USSS the Shipment Document was not posted
    successfully.

    Similar success case in system for this type: PO 3563311529


    Shipment is being posted by USBATCH through Inbound IDOC which when processed without errors,
    shipment is posted.

    You might also like