IDOC performance for inbound materials

I am attemting to load 17,500,000 material into our production system.
We will be loading them through our PI system.
Does anyone know what should be tuned to ensure the Inbound IDOC is processing quicky.
I have already decided to use packets to load inbound IDOCS from PI however I want to know of any else I need to optimize so my inbound loads are really fast.
Thanks in advance.
Weyland Yutani

Hi,
Prepare the material DATA in FILE and then use LSMW direct input to upload the file. It will be better approach.
Error handling will be difficult if you use PI for data load.
Regards,
Shanmuagavel Chandrasekaran

Similar Messages

Standard IDoc Type for Inbound NonPO Vendor Invoices - FB60

What should be the perfect standard IDoc Type for Inbound NonPO Vendor Invoice posting. Tcode FB60.
I found IDoc Type FIDCCP02 but the Function Module 'IDOC_INPUT_FIDCC2' for FIDCCP02 is not released.
In the same way many other standard function modules like - IDOC_INPUT_ACLPAY, IDOC_INPUT_FIDCCH, IDOC_INPUT_ACC_INVOICE_RECEIPT and few more are not released.
My question : If at all I have to use standard IDoc Type, Message type and Function module (Released) for Inbound NonPO Vendor Invoices, then what should be the solution from SAP ?
Thanks,
Veeru.

Hi,
IDOC_INPUT_FIDCC2 for FIDCCP02 works for us in ECC6.0
If you want Automatic tax calculation functionality using FIDCCP02.. then FIDCC2 is not correct message type for you. In that case you should probably go for :
Msg: INVOIC
Basic type: INVOIC02
FM: IDOC_INPUT_INVOIC_FI
Process code: INVF
Thanks,
Kumar

When idoc failes for inbound sales orders then how to trigger a mail notifi

Hi All,
When idoc failes for inbound sales orders in SAP then i would like to send an email notificaiton to particular user id. Could you please let me know the settings for this requirement.
Thanks in advance..

Closing thread as there are no replies

Idoc WHSORD for inbound delivery

Hello,
We want to send inbound deliveries to an external WMS (not SAP WM) by using an output in the inbound delivery.
I tried to use idoc WHSORD (basic type DELVRY01) as for Outbound delivery.
I obtained an error message when processing the output : "The message record of the message control contains a partner role with a partner type LS that cannot be used here. Only the 'KU' and 'LI' partner types are allowed."
Configuration done (same as outbound delivery) :
Output : Medium "6 EDI" / Partner type LS
Partner profile (WE20) : Partner type LS / Partner role LS /Message control : Application E1 / process code DELV.
Finally, I've been able to generate one idoc from the inbound delivery by using medium "A ALE" and partner type LI "vendor". But I need to do it for a LS partner as we do want to maintain partner profile for each vendor.
Is this due to some missing configuration linked to application E1 (i.e allow partner type LS ?) ?
How can we solve this ?
Thanks a lot for your help

Hi zhiqiang,
In order to test inbound idocs, you can use transaction WE19 to create manually idocs.
As pre-requisite, you have to maintain ALE configuration : port and partner profiles.
Then in WE19, you can create an idoc from message type : fill all the fields you need to and delete unuse segments. Then click on "Standard inbound" and your idoc will be received in your SAP system.
Check the status in transaction BD87.
To fill correctlly your idoc :
1. You can find documentation on message type in transaction WE60 (when you go in this transaction, check the documention is "active" => Goto => user settings => "Documentation output" and "field value output" must be ticked)
2. In WE19, for some fields, if you press F4, you will get list of possible values.
Good luck,
JP

How to get Get IDOC Number for Inbound IDOCS

Hi,
I am using the FM -- IDOC_INPUT_HRMD for creating Inbound IDOCS.
I populate the values for Control Record and Data Record and the IDOC is posted successfully and i get the status 53 in the status Table.
But the problem is the field for IDOC number(DOCNUM in IDOC_STATUS Table of the FM ) is empty.
How can i get the DOCNUM for the IDOC posted as a result of this FM ?
regards,
Siddhartha

Hi Siddhartha,
I think you cannot call IDOC_INPUT_HRMD fm directly from the external program as this fm only handles the application logic part and not the idoc number generation and save part.
So I think you have to call IDOC_INBOUND_SINGLE from your external program and then get the IDOC number.
Then if you need the status records then you need to call another fm and feed IDOC number that you have got from IDOC_INBOUND_SINGLE (there is one IDOC_READ_COMPLETELY but it is not a remote enabled fm)
OK, I just found one RFC enabled fm which you can use,
EDI_DOCUMENT_READ_ALL_STATUS
Hope this helps..
Sri
Message was edited by: Srikanth Pinnamaneni

IDoc Serialization for Inbound processing

Hi Techies,
I have a requirement of sending the IDocs from XI to SAP in the same order in which they were sent from the sender SAP system.
i have a special constriant here which says "if the message get stuck in the Integration Engine (may be because of any runtime error) the messages sent after this message should not be processed.
How can i achieve this, please help.
Regards,
Jeet

Hi,
This will help you..
http://help.sap.com/saphelp_erp2004/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/content.htm
Setting up inbound qRFC queues for serializing IDocs using the IDoc Adapter
Regards,
Sarvesh

Mapping the IDOC fields for Inbound PO

Hi,
I am trying to map the fields for PO for IDOC type ORDER05, but unable to do so for the following IDOC fields in segments.
Document Date
Vendor
Account Assignment Category
Delivery Date
Requirement No.
Requisitioner
Purchase Requisition
Preq Item No.
Outline Agreement
Outline Agreement No.
What fields in the IDOC match these in SAP R/3.
Thanks,
Randy.

Hi Did you manage to get this IDoc working? I'm having the same problem with the mapping and the documentation is really bad.
Thanks.

Which iDoc/FM for Inbound AB Accounting Document ?

We need to generate an iDoc from an external source which will create an AB Accounting Document in SAP R/3 (transaction would be FB01). There would appear to be various possible candidates with regards to Basic Types, Message Types, Function Modules etc, for example :
Message Basic Type FM
FIDCC2 FIDCCP02 IDOC_INPUT_FIDCC2
ACC_DOCUMENT ACC_DOCUMENT02 BAPI_IDOC_INPUTP
We are running 4.70 110. I would appreciate some guidance as to the most appropriate iDoc/Message/FM to use.
Many thanks,
Paul Read.

Found answer through trial-and-error.

Idoc DELVRY03 for Inbound Delivey

Hi.
Somebody used IDoc DELVRY03 to create Inbound Delivery (instead of transaction VL31N). I'd like to know how to use this IDoc, or where I can find information about it. Thank you.

Hi,
Check this thread
Re: Inbound Delivery via IDoc DELVRY03
Thanks,
Naren

Regarding idoc performance

Hi gurus,
We use idoc adapter in our project, and most of them are inbound idocs.
Some of these interfaces need to be processed realtime, while some of them are set sporadically in WE20.
For realtime interface, we are worried about the performance, as you know each time one idoc only processes one piece of data, and most of standard idocs use 'call transaction' method. Do we have any solution or infrastructure to get a better performance?
In your system, how many idocs will be generated one day? How many of them are realtime and how many are processed by job?
In our system, we estimate there will be average 4000 idocs per day and 10000 idocs at peak. Is it ok for R3 4.7 system?
Any help will be appreciated.

hi,
as per my knowledge , we need to use message pakaging/ idoc packaging(sender) concept .
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30ea2fdf-f047-2a10-d3a2-955a634bde6b?QuickLink=index&overridelayout=true
or
please you ll refer bellow blog:
IDOC performance for inbound materials
thanks,

Step-by step procedure for INBOUND IDOC (VENDOR CREATE / CHANGE)

Hi ,
Can any body provide me the step-by-step procedure for Inbound IDOCS.
As i'm new to this i need the the clarification between Inbound & outbound idocs.
How can we differentiate both?
where to define outbound & where to define Inbound?
( If possible Please explain me the procedure for Vendor Create through INBOUND IDOCS )
Thanks in advance..

Hi,
Ale Technology is SAPu2019s technology to support distributed yet integrated processes across several SAP systems.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocu2019s definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programu2019s design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocu2019s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
u2022 Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
u2022 IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
u2022 Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
u2022 Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
u2022 Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
u2022 Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
u2022 Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
u2022 Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc u2013 Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch u2013 ALE Service).
u2022 IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
Inbound Process in IDocs:
An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
Posting Program:
Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
Workflow:
A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
Partner Profile;
A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
Process flow for the Inbound process via a Function Module:
In this process, IDocs are received from another system and passed to the posting function module directly.
1. Processing in the communication Layer:
The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
2. Processing in the ALE/EDI Interface Layer:
u2022 Basic integrity check: A basic integrity check is performed on the control record.
u2022 Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
u2022 Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc u2013 Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
u2022 IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
u2022 IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
3. Processing in the Posting Module:
The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
The results of execution are passed back via the function moduleu2019s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).

Inbound IDoc used for updating Sales order status

I have a requirements to set use standard IDoc to send out the Sales order to a non-SAP software as well as receiving Inbound IDoc to update the status of sales order in SAP. Could someone comment on my questions below:
1. What are the difference between all the ORDERSxx Idoc types?
2. What IDoc should be used for Inbound IDoc to update the sales order stataus in SAP?
3. Can the same IDoc type be used for both Inbound and Outbound with only the difference in the segment of Direction?
Thank you. Points will be awarded appropriately for helpful comments.

Hi,
1.Intially standard IDOC types "ORDERS01" is having limited
      segments. After few months the requirement got increased to
      add more fields to "ORDERS01".So,once you release the IDOC
      type you can not add any more fields .So SAP come up
      with "ORDERS02" with new fields.Like that all IDocs types have
      some more new seg ments.
2.You can use ORDER05
3. Yes you can use same IDOC type

IDOC for inbound delivery

Hi Gurus,
Pls help me to understand this functionality:
Shipments destined for a Distribution Center will generate ASNu2019s(advance shipping notification) to alert the Distribution Center to the upcoming receipt.
There are two variations of the transaction that will initiate the ASN:
u2022 Receipt of an ASN from a vendor to a Distribution Center will result in the creation of an Inbound Delivery. That Inbound Delivery must be sent to WM via IDOC.
u2022 Shipments from Distribution Center to DC will create an Outbound Delivery from the u201CClose Loadu201D process in Warehouse M. Creation of the Outbound Delivery to another DC is the trigger for the IDOC to WM.
The IDOC to be used could be a variation of the DELVRY03.
My doubts includes:
1. can I use one idoc for both the scenarios?
2. both are outbound idocs or not?
3. Any suggestions how to do this?
Thanks..
SD

>
Shibu David wrote:
> My doubts includes:
> 1. can I use one idoc for both the scenarios?
Yes you can use IDOC DELVRY03 for both scenarios
>
Shibu David wrote:
> 2. both are outbound idocs or not?
No.
ASN sent to DC will be outbound message.
ASN received by DC, which creates Inbound delivery is inbound message.
>
Shibu David wrote:
> 3. Any suggestions how to do this?
As far as I know message type used in SAP for ASN is DESADV.
For inbound ASN use process code DELS and for outbound use DELV

Post Goods Receipt for Inbound Delivery using WHSCON IDoc

Dear All
Currently I am working on a big project dealing with EDI connections to our logistics partner for the Export business. The entire message flow between Lindt and our partner should be via EDI. Our SAP release is (still) 4.6c.
We will create two kinds of despatch advice messages, one for inbound deliveries and one for outbound deliveries for customers.
I would appreciate your support in the following problem that I am facing with the inbound delivery scenario:
We create stock transport orders (purchase orders, POs) for the goods intended to be delivered into the plant at our partner
We create a delivery (type NL = replenishment delivery) for this POs
As soon as we post the goods issue we send the despatch advice (as EANCOM D96A DESADV message) to our partner.
At this point the delivery is basically completed, i.e. packing status (PS) and goods movement status (GM / GS) are equal to 'C' (= completed).
Our logistics partner uses the same EDI message to send us the goods receipts data, e.g.:
We dispatched 50 units of a product => QTY:50:12
The partner received indeed 50 units => QVR:50:66
Please note that we do not use the QVR segment for the quantity difference (between despatched and received quantity) but it contains the received units. This way we avoid negative values in the QVR segment.
When the logistics partner sends back the DESADV message containing the received quantities (QVR segment) we want to make
the goods receipts for the products in the original stock transport order and
upate the message flow in the delivery
My idea was to transform the incoming DESADV message into a WHSCON.DELVRY03 IDoc based on the documentation in: [Delivery Interface|http://help.sap.com/saphelp_crm40/helpdata/en/e2/654b15a9f411d184ec0000e81ddea0/content.htm]
In the delivery header control E1EDL18 I used QUALF = 'PGI' (Post goods issue).
I prepared an inbound WHSCON IDoc according to the documentation mentioned below. I managed to get some feedback from the Idoc processing implying that the system tried to do the goods receipt in the PO but failed.
To make a long story short here are my questions:
Can an inbound WHSCON IDoc used for doing both the goods receipt in the PO and the update of the message flow in the delivery?
Does anybody have an example on how to fill the WHSCON IDoc?
Or is my approach a cul-de-sac ?
Kind Regards
Uwe
PS: A related question can be found here: Goods Receipt in PO AND Message Flow Update in Inb. Delivery using WMMBXY

Hi Uwe,
Can an inbound WHSCON IDoc used for doing both the goods receipt in the PO and the update of the message flow in the delivery?
The binary answer would be no. You should use WMMBXY or MBGMCR instead.
But if we are doing goods receipt against Inbound delivery then answer is YES with additionally E1EDL18-QUALF = 'PIC' populated. But please remember no partial receipt is possible against Inbound Delivery.
We should populate E1EDL20-VBELN with our Inbound delivery number and line item info should go to E1EDL24.
I have done a similar interface recently where we are doing receipt against Inbound delivery. But our case was a bit complex because we had to support against Inbound delivery. So we had to go for a custom solution on top of IDOC_INPUT_DELVRY.
Hope this helps. Let me know if you have more questions.
Regards,
Rudra

Idoc - for inbound delivery order confirmation

Hi,
Can some body give me the idoc for Inbound SO Delivery Order Confirmation and if any BAPI method is there to create Delivery order confirmation.
With Regards
Vasu

Hi Vasu,
Below is the link to find out the IDOC name for ur Inbound IDOC scnario
http://help.sap.com/bp_bpmv130/Documentation/K17_BPP_EN_US.doc
Hope this willl help you.
Reward if helpful.

IDOC performance for inbound materials

Similar Messages

Maybe you are looking for