Create shipment from inbound IDOC SHPMNT05 ?

Hello All,
I would like to create an individual shipment when i receive from a partner an inbound IDOC.
I'm using Message type SHPMNT, Basic Type SHPMNT05, Process Code: SHPM and testing in WE19 via FM IDOC_INPUT_SHPMNT.
How can I start the creation of the shipment with this inbound IDOC ?
Is it possible ? or is it necessary to develop in user-exit the code to create shipment with function module (which one ? BAPI_CREATE_SHIPMENT ?)?
Thanks a lot,
My

Hello Reddy
thanks for your answer.
is there particular customizing to be done ?
i exactly use function BORES_IDOC_INPUT_SHPMNT
The inbound idoc is generated but i have the following status message 51 "Application document not posted"
What does it mean ? a problem of data in the inbound IDOC to create the shipment ?
Thanks a lot
MY

Similar Messages

Prevent the Output Message when creating PO from inbound IDOC

Hi SAP Gurus,
In my project, I have to create PO from inbound IDOC (PORDCR) with a specific Document Type ('099').
Requirement: These PO should not generate the output message while the others (Doc Type # '099') do.
I have the Z fuction module which call BAPI_PO_CREATE for posting IDOC and it works fine.
In the existing system, there are some set up that trigger the output message type for PO (output NEU) when using ME21 or ME22, as a result my PO created with output message.
Can you please advise if there are some way (User Exit?) that prevent the output message in this scenario (specific PO Type) without touching the current Condition setup?
I'm new in MM and really need help!
Thanks,
Elaine.

Hi Vinod,
I really appreciate your anwer. I'm going to explore this with my functional consultant.
Just like to have more questions:
1. Is it easier if we change the existing condition table instead of creating a new routine?
2. There are two forms for routine 101 (FORM KOBEV_101 and FORM KOBED_101). Can you explain to me why we need 2 here for what purpose of each form.
3. In the debug mode by using WE19 to post inbound IDOC, I change the SY-SUBRC = 4 and PO created without output message. Is it the right direction? Anything else I need to pay attention to?
Thanks again.
Regards,
Elaine.

Error determining posting period(infostructure S008,Variant Z2,RC3) while creating Sales orders from Inbound IDOCS

Hello,
I am getting this Error message"error determining posting period(infostructure S008,Variant Z2,RC3)" while creating Sales order from Inbound Idocs in the IDOC,which is affecting sales order creation.
While viewing this Info structure S008, I could see no records have been maintained. Wanted to know the reasons behind this Hard error?
Is it something related to Date Field used in the Update Rules for this Infostructure which is causing this posting period error?
Appreciate your inputs on this.
Thanks and Regards
Mohammed Roshan

Thank you Jelena,I checked the Ship. Delivery dates in the IDOC which are for Current Fiscal Year- 20140703 and 20140711,Could there be any other reason for this error?
Could it be an issue with e Update rule in this Infostructire S008
Secondly when we try change the update rule thru MC25 for this Infostructure S008,It gives a message"
"Maintenance of SAP standard updates not allowed"
Kindly advice
Thanks and Regards
Mohammed Roshan

Creating inbound delivery without reference to PO - from inbound idoc

Hi guys,
I have a scenario wherein I need to create inbound delivery from inbound Idoc from external system without reference of PO. There is no PO created in SAP and this inbound delivery will be used just to receive material (purely for logistic purpose).
I have identified DELVRY03 or 05 as Idoc type but I am not sure whether system will create inbound delivery without having reference PO. I have two questions here -
1. Can we create inbound delivery without reference to PO?
2. If yes, which Idoc type should I use to create such inbound delivery?
Please help.
Thanks,
Parimal.

Dear Parimal,
In standard, An inbound delivery can be created as follows:
With reference to a purchase order
With collective processing for several purchase orders
With reference to a stock transport order
With reference to a customer return

Sale Order from Inbound IDOC

I am testing creating Sale Order from inbound IDOC with WE19.
Partn. number = AAA001
Partn. type = KU
Partn.func = PY
Message Type = ORDERS
Process Code = ORDE
I get message 51 "Error: Application document not posted" in IDOC status:
VKORG, VTWEG, SPART cannot be determined for customer AAA001 , vendor
Message no. VG 204
Diagnosis
No sales organization, distribution channel or division were sent to the
    IDOC. This data is necessary if a sales order is to be added
    automatically. If this data is unavailable, you cannot create a sales
    order document.
Procedure
If data on the sales organization, distribution channel and division
    have not been entered in the IDOC, it must be determined using a user
    exit defined in the program.

I will receive IDOC from external non-SAP system.
How can i populate E1EDK14 segment with appropriate values:
E1EDK14 -QUALF = 006
E1EDK14 -ORGID = Division (VBAK-SPART)
E1EDK14 -QUALF = 007
E1EDK14 -ORGID = Distribution Chanel (VBAK-VTWEG)
E1EDK14 -QUALF = 008
E1EDK14 -ORGID = Sales Organisation (VBAK-VKORG)
If external system does not know this values?
Edited by: S S on Feb 28, 2009 12:46 PM

I can create material using inbound Idoc of type MATMAS01, but not MATMAS05

I can create material using inbound Idoc of type MATMAS01 in WE19, but MATMAS05 failed. In fact I used same data ( different material number), and same inbound function, but got different result.
What is different between MATMAS01 and MATMAS05? Is there some configuation need for MATMAS05?
My system is ECC5.0. Thanks.

Hi, nagaraj
this is inbound IDoc, not outbound IDoc, so we can't assign Basic type in WE20, only can assign Message type.
In WE82, there are 5 records about Messagetype MATMAS:
     Message type   Basic type     Release
      MATMAS         MATMAS01        30A
      MATMAS         MATMAS02        30D
      MATMAS         MATMAS03        40A
      MATMAS         MATMAS04        46C
      MATMAS         MATMAS05        470
   I think it should be ok.
In WE57, there 2 records are exist:
   FM_name                 BasicType       MessageType
IDOC_INPUT_MATMAS01       MATMAS01         MATMAS
IDOC_INPUT_MATMAS01       MATMAS05         MATMAS
so I think all configurations should be ok.
Message was edited by:
        liu bin

Moving shipment data using IDOC SHPMNT05

Hi guys,
I want to configure ALE process across two SAP systems and moved shipment data using IDOC SHPMNT05.
May I know how to do that.
Plz help me...................
Thankz in advance,
Swetha.

Hi Shwetha,
Please check the following links to start with.
http://help.sap.com/saphelp_nw04/helpdata/en/78/217da751ce11d189570000e829fbbd/content.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
Thanks,
Naren

Issue while trying to create Sales Order from Inbound Idoc ORDER05

Hi All,
I am trying to create a sales order through an Inbound idoc ORDERS05 created out of a Purchase order. The header pricing conditions from the Purchase orders gets populated in E1EDK05 segment and this needs to go to the Sales order header conditions while trying to create the Sales order.
But when the fields are getting incorrectly mapped to the Sales order. Issue being, the segment E1EDK05-BETRG contains the condition value. But this fields gets populated to the KOMV-KWERT (condition value) screen field on the Sales order header conditions. But this should have got mapped to field KOMV-KBETR (Rate). If I look at the Purchase order, E1EDK05-BETRG is the field getting fetched from field KOMV-KBETR on the Purchase order. So this should have correspondingly got mapped to KOMV-KBETR on the Sales order as well.
This looks like a standard behavior. But if any of you have encountered this issue before please let me know if any Correction instructions are available for the same. If this some issue in Pricing conditions configuration, do let me know.

Hi Paaavan
You can set a break-point include "FV45PFAP_VBAP_BEARBEITEN_VORBE" that is called by both the SAP Standard and BAPI where the data is prepared and checked in the internal table XVBAP. Compare both SAP standard VA01 and your 'Z' program for what may be different in XVBAP.
I think the problem my be with regards to the business_object number that is hardcoded in the standard function module. It has given me issues before and hence I tend to use the function module SD_SALESDOCUMENT_CREATE to create sales documents with.
Regards,
Marius

Creation of Sales Order and Service Contract from Inbound IDOC

Hi Experts,
My requirement is to create a Sales Order as well as a Service Contract from one Inbound IDOC. I am getting the Inbound IDOC from a third Party. The message type is ORDERS and Basic Type is ORDERS02. How ever i am using an extension type IDOC which carries all the required data for Sales Order and Service Contract. My requirement is like, to create a Sales Order first.
I have created a Z FM which is attached to the Process Code and subsequently to the message type. Inside the FM i an calling FM 'IDOC_INPUT_ORDERS' for creation of Sales Order. After that i am changing the IDOC data for the Document Type. I am changing the document type which is responsible for Contract Creation.
Then I am again calling the FM 'IDOC_INPUT_ORDERS' for creation of Contract with the help of IDOC data. But here the Contract is not getting created. It's getting failed during the Batch input session.
I need to solve this problem as soon as possible. Please help me. If there are any other options also please share.
Thanks in Advance.
Regards,
Priyabrata

Actually there is problem with BDCDATA. Inside the FM it's calling transaction with help of BDCDATA. If i am creating a Sales order or contract alone its creating successfully. But when i am trying to create both, it's retuning sy-subrc '1001' after calling the transaction on the second attempt. Is there any problem with BDCDATA like we can't handle with less time gap? Please help and give your inputs.
Regards,
Priyabrata

Creation of Service Contract from Inbound IDOC

Hi Experts,
I am using Inbound IDOC type ORDERS02 with message type ORDERS for creation of Sales Order. Now my requirement is like to create a Service Contract from that Inbound IDOC. The IDOC type contains all the data require to create a Service Contract. The scenario is like, after creation of Sales Order it will check for the corresponding Service Contract exits or not by querying on a Z table which contains all those entries.
So my idea is to create a Z Program, in which it will check for the Service Contract and will create the same by reprocessing the same IDOC or by calling some Function Module. Please suggest how shall i proceed to create a Service Contract.
Is there any way to reprocess the IDOC or to collect the Data from the IDOC segments pass them to a FM which is responsible for creation of Inbound IDOC. Please suggest if this is feasible.
Thanks in Advance.
Regards,
Priyabrata.

Actually there is problem with BDCDATA. Inside the FM it's calling transaction with help of BDCDATA. If i am creating a Sales order or contract alone its creating successfully. But when i am trying to create both, it's retuning sy-subrc '1001' after calling the transaction on the second attempt. Is there any problem with BDCDATA like we can't handle with less time gap? Please help and give your inputs.
Regards,
Priyabrata

Updating transaction MD61 using information from inbound IDOC

Is there any standard IDOC type for Planned Independent Requirement(having fields of table PBED and PBIM in its segment)?If such an IDOC type doesnt exist then i have to go for custom idoc type creation
I have an inbound IDOC having 4 fields in its segment
1.SAP Material number
2.Plant
3.Plant Quantity
4.Requirement date
Now i have to use this information in IDOC to update transaction MD61(create a planned order).
constraints:
in MD61 screen1
SCREEN 1
Material radio button is defaulted to on. This must also be set in the interface. Material number will be valued from the input file.
Plant will be valued from the input file.
Version number defaults to 00, so that value should also be used for the interface.
Planning Horizon From and To dates will be the same date and valued from the input file.
Planning Period should be set to D for Day
SCREEN 2
Material number should default from SCREEN 1 input. The interface should also do this.
MRP Area will default from the Plant on SCREEN 1 input. The interface should also do this.
Version will default from the 00 on SCREEN1. If needed on interface, also default to 00.
Version Active checkbox will be checked by default.
Base Unit of Measure will default from material master.
Only a single date column will appear which should be the date input on SCREEN 1. Value this column with the quantity from the input file.
Input fields are highlighted in screenshots below.
After input is complete, use the SAVE icon to store the data.
Kindly tell me the approach to prepare this interface?

Done,used BAPI_REQUIREMENTS_CREATE TO DO SO

Item text not getting copied into sales order from inbound Idoc

Hi All,
I have a scenario where in we get the sales order created through a inbound 850 idoc .
The trading partner sends the sales order information which gets through GENTRAN and gets posted as inbound idoc in SAP .
The problem here is that ,there are segments with values for item text in the idoc ,but the item text is not getting carried over to the sales order which is getting created because of this idoc.
There is no problem with the header text and it is present both at the idoc as well as the sales order level.
I have checked the configuration for text determination and everything looks fine .
Please let me know has anyone come across a scenario like this .This is important as our EDI is getting failed when an outbound 810 is sent from SAP for the simple reason that there is no item text .
Thanks
Sridhar

Hello Sridhar
Do you have access to the genuine 850 EDI message? Does it contain the item texts? If so then there is probably a problem with the (XSLT) mapping EDI 850 -> ORDERS.ORDERS05 IDoc.
Are you able to test the mapping independent of the EDI transmission? This way you could nail down the problem.
Regards
Uwe

Change sales order values from Inbound Idoc

Hi all,
     In my scenario i have to change sales document automatically(Workflow) by getting the values from the inbound idoc ordchg (one more thing i dont want to create another sales document). Is there is any function module? please tell me how to do this.
Regards,
Adithan S.

Hi Adithan;
   You can read the IDoc information using the function IDOC_READ_COMPLETELY as demonstrated in the example below:
DATA: int_edidd TYPE STANDARD TABLE OF edidd WITH HEADER LINE,
       wf_docnum type edidc-docnum.
MOVE: 'IDOC_NUMBER' to wf_docnum.
CLEAR int_edidd.
REFRESH int_edidd.
CALL FUNCTION 'IDOC_READ_COMPLETELY'
     EXPORTING
          document_number         = wf_docnum
     TABLES
          int_edidd               = int_edidd
     EXCEPTIONS
           document_not_exist      = 1
           document_number_invalid = 2
           OTHERS                  = 3.
   After that call, you can loop through int_edidd to get at the segment information you need.
   You can update the sales order using BAPI_SALESORDER_CHANGE. Below is an example of updating line 10 of a sales order with a new material number.
DATA: l_vbeln LIKE bapivbeln-vbeln,
      so_headx TYPE bapisdh1x,
      change_return LIKE bapiret2 OCCURS 0 WITH HEADER LINE,
      so_item_in TYPE bapisditm OCCURS 0 WITH HEADER LINE,
      so_item_inx TYPE bapisditmx OCCURS 0 WITH HEADER LINE.
MOVE 'U' TO so_headx-updateflag.
MOVE <insert sales order number here> to l_vbeln.
MOVE: '00010' TO so_item_in-itm_number,
       'MATERIAL_NUMBER' TO so_item_in-material.
APPEND so_item_in.
MOVE: '00010' TO so_item_inx-itm_number,
      'U' TO so_item_inx-updateflag,
      'X' TO so_item_inx-material.
APPEND so_item_inx.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
     EXPORTING
          salesdocument    = l_vbeln
          order_header_inx = so_headx
     TABLES
          return           = change_return
          order_item_in    = so_item_in
          order_item_inx   = so_item_inx.
Cheers,
John

Overwriting the Gross-Weight (E1VPDLI-BRGEW) from inbound idoc sdpiid01

Hi All,
We are creating document to update confirmation quatities in SAP with inbound idoc SDPICK.SDPIID01 from 3rd party system using XI. We have the correct Gross-Weight(E1VPDLI-BRGEW) in the Idoc, but while posting into SAP, the value getting over-write with I guess net weight. Does anybody know how to stop this Gross wt thing to overwtrie?? Any userexit that I could use for the same???
Regards
Navin

.

How to find Outbound Idoc number from inbound Idoc number.

Hi,
I have one inbound Idoc in my system, then
How to find the idoc number from the system which sends that idoc(Outbound Idoc number).

Hello
You can use fm SREL_GET_NEXT_NEIGHBORS for this purpose.
Scenario: An EDI purchase order is received by SAP-XI and forwarded as Inbound ORDERS IDoc to R/3. SAP-XI generates an (outbound) IDoc number which differs from the (inbound) ORDERS05 IDoc in the R/3 system.
Calling fm SREL_GET_NEXT_NEIGHBORS with the following parameters:
OBJECT-OBJKEY = <IDoc number, 16-digits>
OBJECT-OBJTYPE = 'IDOC'
MAX_HOPS = '99'            " <<< get all links
I get the following result:
0000000000133906                                   IDOC       CUSTOMER   OUTIDOC
0000000000407402                                   IDOC                  INIDOC
000000370383                                       BUS2012    CUSTOMER   OUTBELEG
0010057944                                         BUS2032               INBELEG
Outbound IDoc number
Inbound IDoc number (ORDERS05)
PO number
Sales order (created from inbound ORDERS IDoc)
Regards
Uwe

Create shipment from inbound IDOC SHPMNT05 ?

Similar Messages

Maybe you are looking for