IDoc SHP_OBDLV_CHANGE01 / BAPI_OUTB_DELIVERY_CHANGE

I want to make a batch split on an outbound delivery.
I can't find documentation on IDoc SHP_OBDLV_CHANGE01 or BAPI_OUTB_DELIVERY_CHANGE on which fields to fill.
I have a delivery with 1 item - posnr 10. On this item I wan't to update the quantity and make a batch spilt.
When I try the quantity on the main position is updated but the batch spilt item is not beeing added and I get an errormessage : Text ID language not found

FYI
BAPI_OUTB_DELIVERY_CHANGE
You can BAPI to the extradition change functionality with this method both in the Enterprise-Resource-Planning-system (ERP-system) and in the decentralized Warehouse-management-system (World Cup) extradition after its distribution at the decentralized World Cup change. They can such a change both in the central ERP-system and in the decentralized World Cup carry out. The interface places adjust identically are certainly, that that for one planned extradition data also after a retroactive change in both systems. Change of head data: You delete can delete weight (gross weight and net weight) volume gate delivery appointment delivery priority route Incoterms Abladestelle delivery deliveries only then in the decentralized system and transmit this cancellation at the central SAP-ERP-system if the decentralized World
Cup is a strange system. Set in addition the mark DLV_DEL in the parameter HeaderControl. Change of position data: Quantity of weight (gross weight and net weight) volume decay date position delete change of partner data: Partners to a partner roll change or delete change address of a partner if you would like to change partner data, tests the system in the customizing of the respectively other system whether such a change is permitted. Change flow 1. they change retroactively an extradition in the central ERP-system or in the decentralized World Cup after it was distributed at the decentralized World Cup. 2. If it concerns in the decentralized World Cup a SAP-system, the system blocks the corresponding extradition in the partner system as soon as you call the change transaction. 3. If you secure the change
of the extradition, the system sends a synchronic change request at the connected partner system.
4. The partner system the change simulates based on the synchronic change request and accepts the change request or leans it off. 5. If the partner system rejects the change request, you cannot carry out the change. The system interrupts the preparation and brings a corresponding error message. 6. If the partner system accepts the change request, the system secures the extradition change in the system, in which you carried out the change, and an Asynchronous change request sends at the partner system. 7. Based On the Asynchronous change request, the partner system updates the extradition data. 8. The system the systemübergreifende barrier cancels for the changed extradition. Example if you would like to change for a distributed extradition the quantity, are the following statements for the transmission at the connected system necessary:
in the parameter head data of the extradition (HEADER_DATES) the delivery number (DELIV_NUMB) in the parameter position data of the extradition (ITEM_DATES) the delivery number (DELIV_NUMB) the delivery position (DELIV_ITEM) the delivery quantity in sale quantities unit (DLV_QTY) the Lieferistmenge in basis quantities unit (DLV_QTY_IMUNIT)
the sale quantities unit (SALES_UNIT) the ISO-code of the sale quantities unit (SALES_UNIT_ISO) the basis quantities unit (BASE_UOM) that Make, receives the system the material number, the work, the quantities statement as a floating decimal number, the volumes, the weights and its units out of the underlying extradition record.
References changes of the pack data are not synchronized in the central ERP-system.
In the retroactive change of a distributed delivery, the following prerequisites must be fulfilled:
All positions of the distribution relevant delivery have a joint decentralized administered warehouse number. They generate a distribution model for deliveries. You find generate further information in the introduction (IMG) under Logistics Execution -> integration decentralized World Cup -> headquarters settlement -> distribution -> distribution model. They have define determined in the customizing of the delivery under deliveries -> delivery type -> distribution mode whether the system should distribute the delivery either automatically after record creation or whether the distribution is supposed to be held back, so that you can activate the distribution over the delivery monitor. If you use a strange system as decentralized World Cup, must be guaranteed on sides of the decentralized World Cup over a barrier draft that you cannot process a delivery simultaneously in both systems. You find further information to the systemübergreifenden barrier in the SAP-library under basis -> client-server-technology -> Cross-system curl (CSL). If you use the Asynchronous interface for the actual transmission of the extradition change, (IDoc-type SHP_OBDLV_CHANGE), you note the correct IDoc-Strukturdefinition in the construction of the change-IDocs. Eighth you above all on that to exchange the segment sequence not.
Chargensplit in the decentralized World Cup if you change an appointment lower position of a distributed extradition in the decentralized World Cup, is this appointment lower position in the central ERP-system already available. The fields HIERARITEM and USEHIERITM are empty. The system receives the appointment lower position into the field DELIV_ITEM. If you change the quantity of an appointments head position of a distributed extradition in the decentralized World Cup, this appointments head position in the central ERP-system is already available. The fields HIERARITEM and USEHIERITM are empty. The system receives the appointment lower position into the field DELIV_ITEM. If you carry out in the decentralized World Cup a Chargensplit for a distributed extradition, only the appointments head position is at this time available in the central ERP-system. If you design for example two appointment lower positions, emerge for the transmission at the central ERP-system three
Position segment ItemData: The position segment for the appointments head position HIERARITEM is empty. The delivery quantity and the basis quantity are empty. Per appointment lower position, a position segment with the following fields emerges: DELIV_ITEM contains the number of the appointment lower position. HIERARITEM contains the number of the appointments head position. USEHIERITM indicates the use of the lower position with the value 1 as an appointment lower position. The quantities fields correspond to the quantities in the appointment lower positions. The central ERP-system carries out corresponding to the Chargensplit retroactively for the distributed extradition.
Parameter HEADER_DATES HEADER_CONTROL DELIVERY TECHN_CONTROL HEADER_PARTNER HEADER_PARTNER_HEADER
HEADER_DEADLINES ITEM_DATES ITEM_CONTROL ITEM_SERIAL_ITEM SUPPLIER_CONS_DATES EXTENSION1 EXTENSION2 RETURN
TOKENREFERENCE Exceptions function group V50I
Hope thisll give you idea!!
Pl... award the points.
Good luck
Thanks
Saquib Khan
"Some are wise and some are otherwise"

Similar Messages

Problem WIth BAPI_OUTB_DELIVERY_CHANGE

Hi All,
I want to change the Item level Delivery Quantity in VL02N. I tried to use BAPi_OUTB_DELIVERY_CHANGE. But i did not succeed. I am passing the below parameters.
HEADER_DATA -
> Delivery Number
DELIVERY -
> Delivery Number
ITEM_DATA -
> DELIV_NUMB(Delivery Number), DELIV_ITEM(Item), MATERIAL(material), DLV_QTY(Qty what i need to update in VL02n), FACT_UNIT_NOM(as 1), FACT_UNIT_DENOM (as 1), SALES_UNIT(VRKME), BASE_UOM(MEINS)
ITEM_CONTROL -
> DELIV_NUMB(delivery Number), DELIV_ITEM(Item), CHG_DELQTY(as 'X')
im passing the above parameters to change the delivery quantity at item level . where as im not at all succeding to change the delivery qty.
<REMOVED BY MODERATOR>
Thanks,
Srinivas.
Edited by: Alvaro Tejada Galindo on Apr 7, 2008 5:24 PM

Please, see de function module documentations. The example in red color.
If you want to change the quantity for a distributed quantity, then following entries are required for the transfer to the connected system:
In the header data of outbound delivery parameter (HEADER_DATA)
The delivery number (DELIV_NUMB)
In parameter item data of outbound delivery (ITEM_DATA)
The delivery number (DELIV_NUMB)
The delivery item (DELIV_ITEM)
The delivery quantity in sales unit (DLV_QTY)
The actual delivery quantity in base UoM (DLV_QTY_IMUNIT)
The sales unit (SALES_UNIT)
The ISO code for the sales unit (SALES_UNIT_ISO)
The base unit of measure (BASE_UOM)
The ISO code for the base unit of measure (BASE_UOM_ISO)
In the control of the outbound delivery at item level parameter (ITEM_CONTROL)
The delivery number (DELIV_NUMB)
The delivery item (DELIV_ITEM)
The Change Delivery Quantity indicator(CHG_DELQTY)
If you do not make any further entries, the system copies the material number, plant, quantities as floating point numbers, volumes, weights, and their units from the original outbound delivery document..
Notes
Changes to the packing data are not synchronized in the central ERP system.
For subsequent changes to a distributed inbound delivery, the following prerequisites must be fulfilled:
All items in the distribution-relevant inbound delivery have the same decentrally-managed warehouse number.
You have generated a distribution model for inbound deliveries. For more information, see the implementation guide (IMG) under Logistics Execution -> Decentralized WMS Integration -> Central Processing -> Distribution -> Generate Distribution Model.
In Customizing for Shipping under Deliveries -> Define Delivery Types -> Distribution Mode, you have specified whether the system should distribute the delivery automatically after document creation, or whether distribution should be suppressed so that you can trigger distribution yourself using the delivery monitor.
If you use an external system as the decentralized WMS, you must ensure that there is a blocking system for the decentralized system, which prevents a delivery from being processed in both systems at the same time. For more information on the cross-system lock, see the SAP Library under Basis -> Client-Server Technology -> Cross-System Lock (CSL).
If you use the asynchronous interface for the actual transfer of the outbound delivery changes (IDoc category SHP_OBDLV_CHANGE), you must make sure that the structure definition of the IDoc is correct as you construct the IDoc. You should take particular care not to switch the segment sequence.
[]'s.
Marcus Farias.
Edited by: Marcus Farias on Apr 8, 2008 8:48 AM

Updating sales unit VRKME via IDOC DELVRY03

Dear All,
I am using IDOC : DELVRY03 , message type SHPCON for updating picked quantities for outbound deliveries from an external WM system.
Our delivery quantity is defined in sales units (for example : 1 box which contains 10 PC). PC is the base unit of measure for the product.
Sometimes there is not enough stock in the warehouse so they can pick less then 1 box, for example : 8 PC.
In that case I need to update the picked quantity from 10 to 8 and also update the unit for the delivery from box to PC.
IDOC DELVRY03 does not update the delivery unit even that the field is defined in segment : E1EDL24-VRKME.
Does anyone knows how can I update this field using an IDOC ? BAPI ? or any other option ?
Thank you very much,
Miriam Harel.

Hi Miriam,
Welcome to SDN.
Please try BAPI BAPI_OUTB_DELIVERY_CHANGE to update the sales unit.
Hope this will help.
Regards,
Ferry Lianto

Purpose of BAPI_OUTB_DELIVERY_CHANGE

Hi All,
Can any one explain me why we need to use BAPI_OUTB_DELIVERY_CHANGE. My scenario is like, when partial picking done, need to update the Delivery document with that quantity, which is there in the Inbound Idoc. After that i found that they were using this BAPI in customized program, i could not able to understand why they are using this...can any one explain me.
Thanks
Jayasri.

Ankit,
The BADI - SMOD_V50B0001 will be triggered if the Extension Tables are filled.
Method EXIT_SAPLV50I_010
Should do the trick.
Todd

Query in IDOC.

Hi,
Could you please clarify me the following
1) In which transaction code we can find the all the segements assigned to a MEASSAGE type.
2) In which transaction code we can find all the fields available under the Segement type.
3) where we can see all the MESSAGE types avaialble for a IDOC type.
What are all the different message types available for DELVRY03.
and what are all the MESSAGE types available for DELVRY01
In which scenario we use them.
In which scenario we use DELVRY01 and DELVRY03.
IDOC type SHP_OBDLV_CHANGE01 is used in which scenario and what are all the message types available for this.
Please clarify me.
Thank you.

Hi Anil,
Following below are the details for the queries you have asked;
1) In which transaction code we can find the all the segements assigned to a MEASSAGE type.
Ans: The segments are not assigned to the message type. The segments are assigned to the idoc type (Basic type) and this is inturn assigned to the message type. The tcodes for assigning the segments for the idoc type is [WE30]. and then the tcode for seeing what idoc types are assigned to the message type is [WE82].
2) In which transaction code we can find all the fields available under the Segement type.
Ans: To see the fields in ta segment is [WE31].
3) where we can see all the MESSAGE types avaialble for a IDOC type.
Ans: Tcode [WE82] to see all message types available for the idoc type.. or you can also check in the table EDIMSG.
4) What are all the different message types available for DELVRY03.
Ans: Below is the list of standard message types available for the DELVRY03.
CARNOT
DELTRX
DELVRYASN
DELVRYPSN
DELVRYZSDL
DESADV
SHPCON
SHPCON_GD
SHPORD
STPPOD
WHSCON
WHSORD
5) and what are all the MESSAGE types available for DELVRY01
In which scenario we use them.
Ans: The standard message types available for the DELVRY01 idoc type are as below;
CARNOT
DESADV
SHPCON
SHPORD
WHSCON
WHSORD
The scenario in which this is used is very company specific.. It depends on the segments and fields of the idoc type DELVRY01. If the available segments of the idoc type DELVRY01 suffice the requirements then it is used. But usually the latest version available in the system is used and the segments and fields which are not relevant to the requirement are left off by indicating the segment as "not mandatory".
6) In which scenario we use DELVRY01 and DELVRY03.
Ans: Answered in Point 5... The same holds good for DELVRY03 idoc type.
7) IDOC type SHP_OBDLV_CHANGE01 is used in which scenario and what are all the message types available for this.
Ans: To answer this, I would require to know the SAP version you are working on...Please reply with the info to help me answer this...But as far as my understanding on this goes... this is related to shipping information data interchange, like the shipping notification, etc..
Regards,
Fazal

Inter company / ale idoc

hi pro's
well we are mapping this scenario can u please help me .. like we are getting the stock from japan to india as a intercompany sale . ok now both are distributed systems. so in this process
order is done at india ( va01 ) .
then transfered to japan and wrf to tht order shiping is done from japan (vl01n)
wrf to this del a invoice is created vf01 india.
then an intercompany invoice comes from japan to india ( vf01 IV )
apart from this what is the document ( if there is any ) document which says that japan plant has sent stock to the indian customer.......please lemme knw
how to configure this scenario using idocs ,,,,,please let me know
[email protected]
thanks & regards.

HI
Customer has a separate SAP Warehouse Management System (WMS) in the R/3 landscape where all R/3 Distribution data are replicated/distributed from R/3 to the WMS system via ALE. For example, Sales Orders are created in R/3 - when they are delivered (Sales document->Deliver) the ALE kicks in and the same Delivery doc is distributed to the WMS system but the Sales order is not distributed. Any subsequent functions for the Delivery like Picking, Packing, Goods Issue, Shipment is then done from the WMS system only so that all distribution specific transactional data are stored and processed from the WMS system.
Again, in order to successfully distribute the delivery documents to the WMS system from R/3 via ALE, a lot of SD master data needs to be distributed prior to these subsequent distribution business processes (like picking, packing, GI etc.). So another set of ALEs are also set up to distribute SD master data via IDocs (within the ALE framework) to the WMS system everytime master data is created/changed in the R/3 - for example - Plant, Warehouse, Storage Type, Storage Location, Material Master etc.
Hope this helps as an example to understand the usability of the ALE technology.
For distribution of materials from R/3 to WMS, we use Basic Type/IDoc Type MATMAS05, Message Type MATMAS. We've set up MATMAS05 using ALE Filters on Division, Sales Org., Distribution Channel, Material Type, Storage Location and Plant as we want only specific org data to distribute across WMS.
For delivery document change and replication, we use BAPIs via the Distribution Model (transaction BD64). Here we've associated BAPI_INB_DELIVERY_CHANGE for change of inbound deliveries, BAPI_INB_DELIVERY_SAVEREPLICA to save replica of inbound deliveries, BAPI_OUTB_DELIVERY_CHANGE for change of outbound deliveries and BAPI_OUTB_DELIVERY_SAVEREPLICA to save replica of outbound deliveries. Again, on each of these methods, we use ALE Filter groups to replicate/update changes related to particular business org. data.
REFER LINK BELOW
http://www.erpgenie.com/ale/index.htm
Sail

BAPI_OUTB_DELIVERY_CHANGE

Hi,
Can any one pls help me with an example code for BAPI_OUTB_DELIVERY_CHANGE for batch splits?
Thanks

Hi Prabha,
    You can use this BAPI to change outbound deliveries in both the
    Enterprise Resource Planning system (ERP system) and the decentralized
    Warehouse Management System (WMS), according to their respective
    distribution to the decentralized WMS. You can make these changes in the
    central ERP system and in the decentralized WMS. The interface ensures
    that outbound delivery data planned for a comparison is identical in
    both systems, even after subsequent changes.
Changing Header Data:
    o   Weight (gross weight and net weight)
    o   Volume
    o   Door
    o   Delivery date
    o   Delivery priority
    o   Route
    o   Incoterms
    o   Unloading point
    o   Delete delivery
        You can only delete deliveries in the decentralized system and copy
        this deletion to the central SAP ERP system, if the decentralized
        WMS is an external system. For this, set the DLV_DEL indicator in
       the HeaderControl parameter.
Changing Item Data:
   o   Quantity
   o   Weight (gross weight and net weight)
   o   Volume
   o   Expiration date
   o   Delete item
Changing Partner Data:
   o   Change or delete partner for a partner function
   o   Change a partner's address
       If you want to change partner data, the system checks the
       Customizing settings of the other system, to see whether this type
       of change is permitted.
   Change Process Flow
   1. You subsequently change an outbound delivery in the central ERP
       system or the decentralized WMS, after the delivery was distributed
       to the decentralized WMS.
   2. If the decentralized WMS is an SAP system, the system blocks the
       relevant outbound delivery in the partner system as soon as you call
       the change transaction.
   3. When you save the changes to the outbound delivery, the system sends
       a synchronous change request to the connected partner system.
   4. The partner system uses the synchronous change request to simulate
       the change, then either accepts or rejects the change request.
   5. If the partner system rejects the change request, you cannot make
       the change. The system cancels processing and displays a relevant
       error message.
   6. If the partner system accepts the change request, the system saves
       the changes to the outbound delivery in the system in which you have
       made the changes. It then sends an asynchronous change request to
       the partner system.
   7. This asynchrounous change request causes the partner system to
       update the outbound delivery data.
   8. The system removes the cross-system lock for the changed outbound
       delivery.
xample
   If you want to change the quantity for a distributed quantity, then
   following entries are required for the transfer to the connected system:
   o   In the header data of outbound delivery parameter (HEADER_DATA)
       -   The delivery number (DELIV_NUMB)
   o   In parameter item data of outbound delivery (ITEM_DATA)
       -   The delivery number (DELIV_NUMB)
       -   The delivery item (DELIV_ITEM)
       -   The delivery quantity in sales unit (DLV_QTY)
       -   The actual delivery quantity in base UoM (DLV_QTY_IMUNIT)
       -   The sales unit (SALES_UNIT)
         -   The ISO code for the sales unit (SALES_UNIT_ISO)
         -   The base unit of measure (BASE_UOM)
         -   The ISO code for the base unit of measure (BASE_UOM_ISO)
     o   In the control of the outbound delivery at item level parameter
         (ITEM_CONTROL)
         -   The delivery number (DELIV_NUMB)
         -   The delivery item (DELIV_ITEM)
         -   The Change Delivery Quantity indicator(CHG_DELQTY)
     If you do not make any further entries, the system copies the material
     number, plant, quantities as floating point numbers, volumes, weights,
     and their units from the original outbound delivery document.
Notes
     Changes to the packing data are not synchronized in the central ERP
     system.
     For subsequent changes to a distributed inbound delivery, the following
     prerequisites must be fulfilled:
     o   All items in the distribution-relevant inbound delivery have the
         same decentrally-managed warehouse number.
     o   You have generated a distribution model for inbound deliveries. For
         more information, see the implementation guide (IMG) under Logistics
         Execution -> Decentralized WMS Integration -> Central Processing ->
         Distribution -> Generate Distribution Model.
     o   In Customizing for Shipping under Deliveries -> Define Delivery
         Types -> Distribution Mode, you have specified whether the system
         should distribute the delivery automatically after document
         creation, or whether distribution should be suppressed so that you
         can trigger distribution yourself using the delivery monitor.
     o   If you use an external system as the decentralized WMS, you must
         ensure that there is a blocking system for the decentralized system,
         which prevents a delivery from being processed in both systems at
         the same time. For more information on the cross-system lock, see
         the SAP Library under Basis -> Client-Server Technology ->
         Cross-System Lock (CSL).
     If you use the asynchronous interface for the actual transfer of the
     outbound delivery changes (IDoc category SHP_OBDLV_CHANGE), you must
     make sure that the structure definition of the IDoc is correct as you
     construct the IDoc. You should take particular care not to switch the
     segment sequence.
     Batch Split in the Decentralized WMS
     o   If you change a batch subitem from a distributed outbound delivery
         in the decentralized WMS, then this batch subitem already exists in
         the central ERP system.
         The fields HIERARITEM and USEHIERITM are empty. The system copies
         the batch subitem in the DELIV_ITEM field.
     o   If you change the quantity of a batch main item from a distributed
         outbound delivery in the decentralized WMS, then this batch main
         item already exists in the central ERP system.
         The fields HIERARITEM and USEHIERITM are empty. The system copies
         the batch subitem into the DELIV_ITEM field.
     o   If you perform a batch split for a distributed outbound delivery in
         the decentralized WMS, only the batch main item exists at that time
         in the central ERP system.
If, for example, you create two batch subitems, three item segments
ItemData are generated for transmission to the central ERP system:
-   The item segment for the batch main item HIERARITEM is empty.
     The delivery quantity and base quantity are empty.
-   For each subitem, the system generates an item segment with the
     following fields:
     DELIV_ITEM contains the number of the batch subitem.
     HIERARITEM contains the number of the batch main item.
     USEHIERITM with value 1 shows that the subitem is used as a
     batch subitem.
     The quantity fields match the quantities in the batch subitems.
The central ERP system performs the batch split subsequently for the
distributed outbound delivery.
Regards,
Hemant

Updating bill of lading on outbound delivery using IDoc/BAPI?

Hi,
We're looking to update our existing outbound deliveries with an entry in the bill of lading field. This is the only piece of data that needs changing in the delivery.
It seems that using IDocs message types like SHPCON/DESADV you cannot just update some header level fields. The BAPI_OUTB_DELIVERY_CHANGE unfortunately does not include bill of lading as one its changeable header fields.
Can anyone recommend a way how to still achieve this?
Thanks a lot,
Ronald

Hm, it looks like that segment should've worked...
WHEN 'E1EDT13'.
S_DT13 = IDOC_DATA-SDATA.
CASE S_DT13-QUALF.
WHEN '006'.
<...>
MV S_DT13-ISDD S_KOKO-WADAT_IST.
Did you put the date in the right field (ISDD) and did you try debugging this?

Trigger SHP_OBDLV_CHANGE from BAPI_OUTB_DELIVERY_CHANGE

Hello.
I'm currently using BAPI_OUTB_DELIVERY_CHANGE (inside a custom function that creates shipments) to update the route, shipping conditions and unloading point of a delivery in a DWMS system. I am successful in updating the deliveries however, the SHP_OBDLV_CHANGE Idoc is not being generated which in turn doesn't update the deliveries in the source system.
My code that calls BAPI_OUTB_DELIERY_CHANGE are as follows:
wa_bapiobdlvhdrchg-route = l_route.
wa_bapiobdlvhdrchg-unload_pt = l_exti2.
wa_bapiobdlvhdrchg-ship_cond = l_vsbed.
wa_bapiobdlvhdrctrlchg-route_flg = 'X'.
wa_bapiobdlvhdrctrlchg-unload_pt_flg = 'X'.
wa_bapiobdlvhdrctrlchg-ship_cond_flg = 'X'.
      CALL FUNCTION 'BAPI_OUTB_DELIVERY_CHANGE'
        EXPORTING
          HEADER_DATA             = wa_bapiobdlvhdrchg
          HEADER_CONTROL      = wa_bapiobdlvhdrctrlchg
          DELIVERY                      = l_vbeln
        TABLES
          RETURN                        = lt_return.
I've read the documentation and it seems that whenever this bapi is used in a DWMS system, it should generate a SHP_OBDLV_CHANGE Idoc.
I also read this from the following link: Very Urgent : Need of Mandatory Fields to be supplied for these BAPI's
I can't find anymore documentation regarding this bapi.
Any kind of help, inputs and suggestions would be appreciated.
Thanks!
Carlo

The MASTER_IDOC_DISTRIBUTE might work.. Interesting.
Oh! Sorry to confuse you. I'll try to explain in a simpler way.
Delivery gets created in R3 (delivery creation always happens in R3 only) -> SAVE_REPLICA idoc goes out from R3 to DWMS -> Delivery replicated in DWMS.
When delivery is modifited in R3 (using VL02N) -> CSL locks the delivery replica in DWMS
When delivery is saved after modification in R3 -> SHP_OBDLV_CHANGE idoc goes out from R3 to DWMS -> Delivery replica will be updated in DWMS.
When delivery is modified in DWMS (using VL02N) -> CSL locks the original delivery in R3
When delivery is saved after modification in DWMS -> SHP_OBDLV_CHANGE idoc goes out from DWMS to R3 -> Original delivery will be updated in R3.
Next section only happens in the DWMS system...
When shipment is created in DWMS, deliveries should be updated in DWMS and R3. The deliveries are being updated in the background using BAPI_OUTB_DELIVERY_CHANGE in DWMS.
SHP_OBDLV_CHANGE idoc should be generated in DWMS to update the original delivery in R3. However, this step is not working (this is my big problem).
And as per documentations that I've read (even the bapi documentation), BAPI_OUTB_DELIVERY_CHANGE should be able to generate the SHP_OBDLV_CHANGE idoc.
I hope that clears things up more.
The thing is though, documentation seems to say that BAPI_OUTB_DELIVERY_CHANGE should be able to generate the SHP_OBDLV_CHANGE idoc but I'm currently using it and it's not doing it. I'm assuming maybe I missed something on the import section of the bapi..
Inputs, help, etc, appreciated.
Thanks,
Carlo

Logical System in IDOC-XI scenario

Hi,
I need help to understand few things in IDOC-XI scenario, could any one help me in this regard.
we use Adapter specific identifiers to map services, we have following type of identifiers 1) Sys.ID & Client No. 2) Logical System.
my questions are
a) Are we use Logical System in B to B scenario ?
b) Are we use LS in reference to the SAP system or Non SAP system ? if a non SAP system....how a non SAP system send an IDOC and why a non SAP system receive an IDOC ( conversion is possible in XI ) ?
Thanks and Regards
Mahesh.

Hay Kumar,
Logical systems can also be used for SAp sytems wich are not installed yet as a virtuall placeholder.
a) yes. if on of your business is a non sap system or a propritery system that you developed yuo'll ue LS.
b) non SAP system can send and recieve IDOCs. so it's possiable to get an IDOC from a system and turn it into an RFC for SAP or get an IDOC from an SAP system and then turn it into something else for another system.
Have a Good One,
Uri Lifshitz.

IDoc not received in MII

Hi All,
I am using SAP MII 12.1.5 Build 87.
I am facing problem with iDoc Listner we have configured iDoc Listner properly in SAP ERP, SAP NW and in SAP MII.
We are able to send iDoc from SAP but we are not able to receive same in MII.
Port and iDoc Server is giving status connected previously it was working fine in SAP MII 12.1.5 Build 83.
Following are the log details for SAP MII Logger as well as SAP NW Log.
SAP NW Log:
Error processing JRA IDOC message
SAP MII Log:
Error processing JRA IDOC message
Error processing JRA IDOC message [server=xxx, client=xxx]
[EXCEPTION]
java.lang.NullPointerException
at com.sap.xmii.ejb.JRAListenerBean.onMessage(JRAListenerBean.java:130)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MessageListenerType.invoke(Interceptors_MessageListenerType.java:110)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Lock.invoke(Interceptors_Lock.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at com.sap.engine.services.ejb3.runtime.impl.MDBProxyInvocationHandler.invoke(MDBProxyInvocationHandler.java:77)
at $Proxy943.onMessage(Unknown Source)
at com.sap.mw.jco.jra.idoc.JRAIDocExtension$IDocMessageHandler.onMessage(JRAIDocExtension.java:72)
at com.sap.mw.jco.jra.JRA$ReaderThread.sendDirectToMdb(JRA.java:6641)
at com.sap.mw.jco.jra.JRA$ReaderThread.sendAsynchRequest(JRA.java:6601)
at com.sap.mw.jco.jra.JRA$ReaderThread.handleRequest(JRA.java:6771)
at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:989)
at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:967)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:142)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:2927)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2659)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2478)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2362)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2207)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:259)
at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:322)
at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:220)
at com.sap.mw.jco.jra.JRA$ReaderThread.run(JRA.java:7260)
at com.sap.engine.services.connector.jca15.work.TaskImpl.run(TaskImpl.java:255)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Please help me out on this issue.
Regards,
Manoj Bilthare
Edited by: Manoj Bilthare on May 19, 2010 12:57 PM

Hi Manoj,
Once you have configured your Listener have you checked pressing the update button and i dont want to ask you which version of NW SP you have installed as you said it was working for you with Build 83, but nevertheless NW SP Level should not be not less than SP3.
If this doesn't help you,please try restarting your server again.
How about the credential editor have you configured this as well?
Regards,
Sudhir Kumar
Edited by: Sudhir Kumar Shambana on May 19, 2010 10:46 AM

Open Sales orders through IDOC

Hi
We are trying to send the list of open sales orders of a customer in an IDOC to the customer. For example, if the customer has got 15 sales order to be delivered to him , he needs the details of all these 15 orders in an single IDOC
Is there any IDOC message type available for this in SAP R/3 4.7 version or is there a standard solution of sending these details through IDOC
Regards
Anandh

Hi
We are trying to send the list of open sales orders of a customer in an IDOC to the customer. For example, if the customer has got 15 sales order to be delivered to him , he needs the details of all these 15 orders in an single IDOC
Is there any IDOC message type available for this in SAP R/3 4.7 version or is there a standard solution of sending these details through IDOC
Regards
Anandh

Scheduling Agreement with Delivery Schedule using Idoc messages

Hi all,
Can anybody please explain the importance of the field name "LABKY" in Idoc execution for Forecaste/JIT Delivery Schedule.
My requirement is that when i send a new Idoc i do not want the old schedule line which are not yet released , to be deleted .
As per the SAP help the use of the field LABKY is related to this , but when i tried its value as "1" , the previous schedule lines are still getting deleted.
Can you pls explain how to go about it . ( DELFOR/DELJIT Idocs)
Thank you
Regards
Subha

Hi ,
The Field
LABKY : Delivery schedule key
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 026, Offset : 0393. external length : 000001
Regards
Seegal

Invoice and delivery notes - idocs..

Hello SD experts,
I am new to SD.
Can any one tell me what is the invoice. I mean
what are the table AND transaction codes I have to go and check ?
What are delivery notes ?
My functional consultant is telling that
there is a consolidated invoice and there are 2 delivery notes that are being combined for this invoice. The invoice # is 6016186004
For DN#   6073107044 there is a VICS BOL that was passed back that is = 04000000000016146
               6073107045 there is a VICS BOL that was passed back that is = 04000000000016023
and he wants to know how the program selects which VICS BOL fields in IDOC. He gave me to use IDOC #77122253 in quality system for testing.
In this case , Idoc checking/testing...I need to go to RSNAST00 program ?
If so then what are the I need to give
Output application    (is it V1 or MR ?)
Output type    ??

hi ..
Please refer below..
for invoice , tables: VBRK and VBRP
AND transaction codes : VF01 to 03.
What are delivery notes ?
after goods issue, we need to issues delivery note to customer.
In this case , Idoc checking/testing...I need to go to RSNAST00 program ?
you need to go to VL70 or you can process with RSNAST00.
Output application type : V2
Output type : LD00
Regards
Venkat.. Ananth Technologies

Error Posting IDOC: need help in understanding the following error

Hi ALL
Can you please, help me understand the following error encountered while the message was trying to post a IDOC.
where SAP_050 is the RFC destination created to post IDOCs
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>FM NLS_GET_LANGU_CP_TAB: Could not determine code page with SAP_050 Operation successfully executed FM NLS_GET_LANGU_CP_TAB</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: FM NLS_GET_LANGU_CP_TAB: Could not determine code page with SAP_050 Operation successfully executed FM NLS_GET_LANGU_CP_TAB</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Your help is greatly appreciated.............Thank you!

Hi Patrick,
Check the authorizations assigned to the user which you used in the RFC destinations, If there is no enough authorizations then it is not possible to post the idocs.
Also Refer this Note 747322
Regards,
Prakash

IDoc SHP_OBDLV_CHANGE01 / BAPI_OUTB_DELIVERY_CHANGE

Similar Messages

Maybe you are looking for