IDOC_INPUT_SHIPPL - Shipment creation/Mod using Idoc

We have set up an external Transportation Planning System. And are trying to create Shipments in SAP using IDOCs from external system.
The External system has been configured. We are now getting an error saying Shipment XYZ has not been saved (V6 513). It does not give any other message other than this.
If we send some error value then the corresponding SAP application error message is shown, along with the above message.
This has eaten my brain for a week. Anyone solved this?

Hi Cyril,
Can you successfully post the IDoc using exactly the same data (for all the segments/fields) that is received from the external system in SAP via transaction WE19? Use the data in one of the failed IDocs to post this in test mode. What message do you get?
Also, I suppose the data is converted to IDoc format from the external system by a middleware? Is this middleware working correctly? To confirm, change SAP settings as not to post the IDoc immediately when received so that you can post it manually using BD87. Before you push it thru BD87, put a break point in the FM IDOC_INPUT_SHIPPL at the very beginning and check the IDoc segments/fields to confirm data is received correctly as SAP expects it. If data OK then put another "break point at message" statement to check what's going wrong.
Hope this helps.
Cheers,
Sougata.
okay, debug the FM then as I suggested above up to the error message.
Don't forget to reward points.
Message was edited by:
Sougata Chatterjee

Similar Messages

Handling unit creation in existing shipment via BAPI or IDOC

Dear all,
Dose any one tried and succeed packing deliveries items in an existing shipment in the shipment level via BAPI or IDOC.
I tried to use IDOC massage type SHPADV. The problem was that it's creates a new shipment with the same deliveries and pack their items, although I entered the existing shipment number.
With regards to "BAPI_SHIPMENT_CHANGE", it is seems like this BAPI is not an option. It is update the shipment in any shipment field but not creating HU in shipment level.
Dose there any solution via those options or there is any other solution.
Thanks in advance,
Itai

I tried simulating this LSMW (message type- PREQCR1, Baisc type -PREQCR101) and it is working fine. I used creation indicator = R in item segment - E1BPMEREQITEM and have not updated value for this field in Header. So try without any value for CREATE_IND in HEADER and just pass R in item.
yogesh

Issue in Creation of shipment with events using BAPI_SHIPMENT_CREATE

Hello experts,
I am trying to create shipments using BAPI_SHIPMENT_CRETAE for which data is provided in an excel.
The issue here is I have to create the events in shipment i.e., I need to fill the Further dates tab. But in this BAPI there is no such structure or field which can take the input and create an entry in this tab. Please let me know if we can do this using this BAPI .
Also let me know if there are any other bapi's for shipment creation or the only way is to go for BDC.
Thanks.

Hi,
The BAPI_SHIPMENT_CREATE can't upload further dates, partners etc.
You can try below options.
1. Use BAPI to create basic shipment and update further dates data through BDC(VT02)
2. Create shipment using BDC(VT01)
Regards
Praveen

Creation of PO using IDOC's

Hi,
I am trying to create a PO, using IDocs, in the SAP system. The IDoc will come from a non-SAP system - hence, this is an inbound interface.
Can someone please tell me which Message Type / IDoc Type I should use?
As well, I need to create Characteristics for the Purchase Order. So, I need an IDoc that allows me to create these.
Two options (using existing IDocs):
1. ORDERS/ORDERS05
I have read some of the help documentation and some of the messages posted on this forum and found that the ORDERS/ORDERS05 is used for outbound PO IDocs, and inbound SO IDocs.
Can someone please confirm or correct me? So, this option is OUT.
2. PORDCR/PORDCR05
Apparently, PORDCR/PORDCR05 can be used for inbound PO. However, it does not contain segments for Characteristics. Hence, I will need to extend the IDoc. However, there aren't any useful user-exits to handle the creation of Characteristic values!
Any ideas or suggestions will be greatly rewarded .
Thanks
Bobby

on your points
#1is correct.
#2 yes, if you need any other functionality you need to extend the IDOC. alternately look at BAPI_PO_CREATE* BAPIs to see if they fulfil your requirements

Error when ECO and BOM creation using IDoc

Hi experts,
now i am doing an interface about ECO/BOM creation and changing using IDoc.The idoc type is ECMMAS02 ans BOMMAT04.
since i know a little about ECO/BOM, can anyone provide some good materials for me?
and i don't know which fields are mandatory in idoc segment, so i go to tansaction BD30 to run a BOM changing. i input a change number but the idoc log shows that change number does not exist. what is the change number using? where i can implement the changes, e.g, change the quantity? should the change number be used when creation and changing? how can i get this change number?
thanks a lot in advance!

Hi experts,
now i am doing an interface about ECO/BOM creation and changing using IDoc.The idoc type is ECMMAS02 ans BOMMAT04.
since i know a little about ECO/BOM, can anyone provide some good materials for me?
and i don't know which fields are mandatory in idoc segment, so i go to tansaction BD30 to run a BOM changing. i input a change number but the idoc log shows that change number does not exist. what is the change number using? where i can implement the changes, e.g, change the quantity? should the change number be used when creation and changing? how can i get this change number?
thanks a lot in advance!

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

Creation of PO/Contract/Scheduling agreement with ref to PR using IDOC

Hi Experts,
Is it possible to create PO/Contract/Scheduling agreement with reference to PR using inbound IDOC ?
If yes, please let me know the segment type and field to be populated for referencing PR in the IDoc .
Thanks in Advance,
Best Regards,
Mitesh Desai

Hi Aarif,
Thanks for taking time to reply .
We are palnning to integrate SAP and non SAP systems.
The business Process is as under .
(1) PR will be generated in ERP (Manaul/MRP)
(2) PR will be coverted into RFQ (for which there is no appropriate source of supply
in ERP)
(3) Sourcing will be done in non SAP system. RFQ will be created with dummy vednro (for example say "source") to identify RFQs to be sent to another system.
These RFQs needs to be sent using IDOC alonwith reference PR numbers and line item numbers.
Multiple PRs will be combined into one RFQ as multiple line items.
(4) Non SAP system will do sourcing and generates either PO or master outline agreement and have reference PR/RFQ numbers and line item numbers.
No SAP system will send PO/outline agreement information to SAP system in XML file format to generate inbound IDOC in SAP .
(5) This inbound idoc will generate PO/outline agreement in SAP.
From SAP functionality point of view, I ca createPO/outline agreement with reference to PR but My Question is how I can generate PO/outline agreement in SAP through IDOC and using "Reference PR or RFQ numbers".
Looking forward to help ASAP.
Regards,
Mitesh Desai

Customer master creation using IDOC

Hi friends,
           I am trying to create customer master into SAP using Idoc. Here pblm is some partner functions already defaulted i want to create some new entries in partner functions when i try to do it online its working fine when i try with idoc the defaulted partner functions are appears double times can any one has any idea whts happening.
E1KNVVM
    E1KNVPM (Master customer master partner roles)
        MSGFN : Function
        PARVW : Partner function
        KUNN2 : Customer number of business partner
        DEFPA : Default partner
        KNREF : Customer description of partner
        PARZA : Partner counter
the pblm is with these segment.
Thanks,
Naren.

Hi naren,
The segment E1KNVPM is standard one.Nothing can be done over it . U shold create new segments in we31 and add as
extension to the basic type and try..
Regards,
Nagaraj

Creation of Delivery Using IDOC without reference to order

Pls suggest is there is any way to create delivery using idoc without reference to order. This is very urgent.

Hi
Design the inbound idoc in such a way that it carries all the essential data needed to create a delivery document namely the material number, no of units to be deilvery, delivering plant, storage location, shipping point, warehouse number(if applicable) etc.
Pass all these details to the function module RV_DELIVERY_CREATE while creating delivery in VL01N and pass the document type as LO which is delivery document without reference to order.
But it is advised to have atleast a pseudo order with which we have to create the delivery document.
Pls reward points.

Regarding Creation of Invoice Verification Document Using Idoc

Hi All,
I am using Idoc INVOICE01 which is getting triggered from one SAP system after Invoice (VF01) is saved.
However this Idoc at the receiving SAP system is not getting posted and is giving error.
I want to post invoiceverification document in the receiving system.
The FM used is IDOC_INPUT_INVOICE_MRM for processing incoming Idoc with process code INVL.
Also I am using Logical System(LS) with ALE Setup fo communications bewteen the two SAP systems.
What sort of functional configurations I need to do to post the Idoc successfully.
I have done the configration for Tcodes OBCA, OCBD, OBCE ??
Do I need to maintain any entry in OBCB ??
Any sample example for this Invoice01 Idoc execution would be of great help.
Waiting for your replies.
Thanks
Jitendra

Hi Jitendra
I did not understand your question at all except your idoc is not posted. Without telling us your error message how can we provide our inputs
What exactly have you done and searched please provide those detail along with error detail rather than these tcode
Nabheet

Customer creation in R/3 from PI data using IDOCs

Hi All,
I am creating customers in SAP r/3 system using IDOCs which are coming from PI system in the form of XML files.
For that DEBMAS and ADRMAS message types and DEBM process code is used for creating or changing customer master data.
Existing functionality : 1 IDOC is creating/changing 1 customer master data using standard function module IDOC_INPUT_DEBITOR.
Required Functionality: need to create/change data for multiple customers using only one IDOC file.
I have tried using DEBMDM. Unlike DEBMAS, message type DEBMDM can hold multiple customers but if any DEBMDM IDOC sent to R/3, it was remaining in status 75 with message 'IDOC Received via qRFC'.
Any help will be appreciated.
Thanks & Regards,
Anshoo

Hi,
Status 75 refers to that "IDoc is in inbound queue".
Transaction SMQ2 (qRFC Monitor - Inbound Queue)
Transaction WEINBQUEUE (IDoc Inbound Queue).
The transactional asynchronous tRFC guarantees that all database operations are fully executed or, if one of the function modules responds with a termination, they are fully rejected (rollback). If an LUW is executed without errors, it cannot be executed again. In some cases it may be necessary, to rollback an LUW in an application program, for example, because a table is locked.
Regards,
Srilatha.

LSMW - Sales Order creation using IDoc

Hello,
I'm receiving a file containing different category of products and need to create a sales order (using IDoc or BAPI) per category. The input file contains UPC code, I use a SELECT statement to check the category and append the UPC code to the specific internal table .(one internal table per category). The issue I have is to do loop in all internal table and then to create a sales order. I have some difficulties to update item segment. Only one UPC is populated to the required segment. Please let me know if this could be done using LSMW.
Thanks ! Thanks ! Thanks ! Thanks !
Mehdi

You can use program RVINVB10 ( Direct Input ) to create Sales Order , Before you run this program you will have to create a file with data in specific format.
Read the documenatation of the program.
LSMw can help in formatting the data but beetr write your own progarm to format data and then run above program as LSMW has limitations and I am not sure what type of file you are getting. In you custom program you will have more control.
Cheers.

Stock Transfport Order Creation using IDOC

Hello Everybody,
I am trying to create a Stock Transport Order using IDOC's. All configuration for the STO has been done and I have no problems creating these orders using ME21N.
Now I need to create STO using IDOC. I am using Message Type ORDERS and Basic Type ORDERS05, but I am not sure what Process Code to use in the Partner Profile configuration in order to pick up proper processing module....
Any help would be appreciated,
Than you in advance
Felix

I ended up writing my own processing FM for this and used BAPI_PO_CREATE1 to post the PO

Using IDOC for PO creation

Hello Experts,
I have to work with IDOC,kindly help me out in urgent basis.
I am using, let, SAVVION as a front-end and SAP as back-end.
Now I have to create PO using standard BAPI, but using IDOC i might be connect two software.
How can i proceed, anybody plz help me out.
will give a best points..
Regards,
Ankur

Hi,
Check this document:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d4ce58df-0901-0010-a4be-9ae9eda61107
cheers
Aveek

Error in creation of PurOrd IDoc

Hi All,
I have set up the output type for PO and created patner profiles and also add the message types ORDER and ORDCHG but when I save the PO and check the messages, I get an error: " No recipient found for message type ORDERS in the ALE Model ".
What could be the possible problem?
Highly appreciate any kind of help.
Thanks in advance,
Shweta
PS: <REMOVED BY MODERATOR>
Message was edited by:
Alvaro Tejada Galindo

Hi
Check the Partner Profile in WE20 correctly
also see the steps for it as per the doc
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
>>>> SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Regards
Anji

IDOC_INPUT_SHIPPL - Shipment creation/Mod using Idoc

Similar Messages

Maybe you are looking for