Inbound idoc monitoring

Dear all
What tcode use for inbound idoc monitoring when data is transfer from one sap system to other sap system
Thanks
Amit

Hi
use the Tool (TCODE WE19) for inbound IDoc monitoring.
Also check the following Tcodes
BDM2 Monitoring: IDocs in Receiving Sys.
ELDM Monitoring of IDocs Processed
IDX5 IDoc Adapter - Monitoring
RSEIDOCA Active IDoc Monitoring with Workflow
WE06 Active IDoc monitoring
Reward points if useful
Regards
Anji
Message was edited by:
 Anji Reddy Vangala

Similar Messages

Error while processing inbound Idoc (HRMDA_07) with FM IDOC_INPUT_HRMD

Hello,
I have a inbound Idoc of type HRMD_A (basistype HRMD_A07) which is processed by Function module (FM) IDOC_INPUT_HRMD with proofing. After processing an Idoc the status Monitor for ALE messages (BD87) tell me that my Idoc has status 53, which should be the result i would like to have.
Unfortunately when i go to transaction PA20 and check the infotypes, i see that infotype 0302 isn't created. When analyzing this problem i see that during the processing the Infotypes are posted with HR_MAINTAIN_MASTERDATA (dialog mode is 0 and luw_mode = 0 from include LRHA2F02 FORM save_pa_pb_infty) When this is done for infotype 0302 sy-subrc <> 0 the message is A complex application error has occured. This error message is placed in Export parameters
Return and Return1
of HR_MAINTAIN_MASTERDATA. When the program returns to the calling Form it checks if there is message of type E in HR_RETURN (see below) :
CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
 EXPORTING
 pernr = ins_objects-objid "#EC DOM_EQUAL
 actio = 'INS'
 tclas = tclas
 dialog_mode = dial_mode
 luw_mode = '0'
 no_existence_check = $cross
 no_enqueue = $cross
 IMPORTING
 return1 = return
 hr_return = hr_return
 TABLES
 proposed_values = proposed_values.
 REFRESH proposed_values.
 IF hr_return-msgty = 'E'. "note 984409
 CLEAR protocol_error.
 protocol_error-msgty = hr_return-msgty.
 protocol_error-msgid = hr_return-msgid.
 protocol_error-msgno = hr_return-msgno.
 protocol_error-msgv1 = hr_return-msgv1.
 protocol_error-msgv2 = hr_return-msgv2.
 protocol_error-msgv3 = hr_return-msgv3.
 protocol_error-msgv4 = hr_return-msgv4.
 READ TABLE t_hrobjinfty WITH KEY objid = hr_return-pernr
 infty = hr_return-infty
 subty = hr_return-subty.
 protocol_error-segnum = t_hrobjinfty-segnum.
 protocol_error-routid = 'create_prf_pa_pb_object'
As mentioned above, the error message is only placed in the parameters Return and Return1 and not in HR_RETURN.please read the first reply

Hi,
I think you have preety much done from your end itself .
Could you please tell me what you got in this parameters:
 protocol_error-msgty = hr_return-msgty.
 protocol_error-msgid = hr_return-msgid.
 protocol_error-msgno = hr_return-msgno.
 protocol_error-msgv1 = hr_return-msgv1.
 protocol_error-msgv2 = hr_return-msgv2.
 protocol_error-msgv3 = hr_return-msgv3.
 protocol_error-msgv4 = hr_return-msgv4.
It may help us to track down the issue in more better way .
Thanks!

IDOC Monitoring issue - job BPM_DATA_COLLECTION* not running.

Hi all,
We are facing an issue with BPM "IDOC Monitoring" (under application monitoring), which we have setup to monitor Inbound and Outbound Idocs in 2 separate R/3 systems.
In one system it works fine, and measured values are returned each time the monitor is set to run according to the specified schedule.
However, for another R/3 system, the monitor has never run, even though the settings are identical in the monitoring setup.
From reading the Interfaces Monitoring Setup guide, I found that this monitor depends on a job called BPM_DATA_COLLECTION* which runs in the monitored system. In the system where monitoring is functioning correctly, I can see this job is completing successfully at the time the monitor is set to run. All I find is completed jobs - no scheduled or released jobs present.
However, for the system where the monitoring is not functioning, I found that this job is not running, but that the job is sitting in scheduled status instead.
When I tested manually running the job in this system, it ran successfully, and in Solution Manager the monitor brought back the measured value, so the monitor only ran successfully when I manually ran the job in the monitored system.
I read notes 1321015 & 1339657 relating to IDOC monitoring. 1321015 appears to be more relevant, yet it does not exactly describe my issue - it mentions the job BPM_DATA_COLLECTION* failing rather than just remaining in scheduled status which is what I see.
Anyone else see this issue before?
On a more general point - the standard BPM Setup guide doesn't really go into much detail on IDOC Monitoring, and makes no mention of what is happening in the background, i.e. the job BPM_DATA_COLLECTION* being created and run as per schedule. This info is found in a separate document "Interface Monitoring Setup Guide".
Is there any single document which describes fully what happens both in the Solution Manager and the Monitored systems when BPM is activated? For example, to describe which monitors require jobs to be run, which monitors require additional setup in monitored system, etc? A document such as this which describes exactly the process flow for each monitor would be very useful in troubleshooting issues going forward.
Thanks,
John

Hello John,
most probably the user assigned to the corresponding RFC READ connection that connects SolMan with the backend system doesn't have proper authorization to release a job. That's why it is only created/scheduled but not released. Verify if the RFC user on the backend has the latest CSMREG profile assigned according to SAP note 455356.
You can also check if the latest ST-PI support package is installed on your backend system as the ST-PI usualy contain the latest definition of CSMREG.
Best Regards
Volker

SM58 - IDoc adapter inbound: IDoc data record table contains no entries

Trying to send Idocs from SAP ECC6.0 via PI 7.0 up until 2 days ago there was no problem.
Since yesterday, only one specific type of Idoc does not make it into XI (PI). In the Idoc monitor (WE02) the idocs that were created gives status 3 which is good. But all Idocs of that specific type (ZRESCR01) does not go to XI. I can only find them bakc in SM58 where it gives the following message:
IDoc adapter inbound: IDoc data record table contains no entries
I have checked SAP notes 1157385 and also 940313, none of them gives me any more insight into this error. I have also checked all the configuration in WE20, SM59, and in XI (repository and directory) and in XI IDX1, IDX2 but could not find anything that would cause this. I can also not think of anything that changed since 2 days ago.
Please point me in the right direction.

hi,
i think in sm 58 u can find entries only when there is some failure in login credential .
if there is change in IDoc structure than you have to reimport the idoc metadata defination at IDX2.otherwise not requird.
please check the logical system name pointing to the your requird target system....
please also verify thet your port should not be blocked.
pls find the link it may help
Monitoring the IDOC Adapter in XI/PI using IDX5
regards,
navneet

Idoc monitoring tool .

Guys , Is there any tool to monitor the Inbound and the outbound IDoc s from one server to another server . ? I know there are transactions to view the Idoc , reprocess it , But i need to know is there any tool kinda thing which monotors all of the inbound and outbound idocs ?

Hi,
I have no idea if there exist such a tool..
But when i had a similar requirement for IDoc monitoring i couldn't find any such tool so i developed a tool on my own similar to WE05 transaction but with additional functionality which will monitor the idocs and email the list of error idocs and complete idoc lists seperately. This tool was scheduled according to the client requirement daily and its working fine now.
Regards,
-Sandeep

IDOC Monitoring urgent

Hi SAPpers,
Does anybody knows what is IDOC Monitoring?
The step by step configuration for IDOC monitoring.
Was is the purpose of that?
What is the Tcode for monitoring IDOC?
Thanks will be rewarded

Hi,
Use
You can easily and effectively monitor inbound and outbound processing of IDocs using special reports and graphic displays. An agent can also be notified automatically using a workflow if an emergency occurs (active monitoring).
Features
The following tools are available for monitoring:
·        IDoc Display
All the other fields of the control record are available as selection criteria as well as partners and messages
-   IDoc numbers
-   Ports
-   IDoc types
You can display a tree structure of the IDoc directly using the IDoc number. The IDoc list is displayed again if several IDocs are selected.
·        IDoc Statistics
The IDocs are sorted and represented graphically according to predefined status groups. Lists and individual IDocs can be displayed using mouse clicks.
·        IDoc Search
You can select IDocs according to their business content, that is, according to the data contained in the segments.
·        Error and Status Processing
Error and status codes are defined for the IDoc transfer. These codes can be assigned to a workflow task, which informs the agent automatically in a procedure.
·        Monitoring the Inbound Queue
If you can receive IDocs via qRFC, you can monitor the inbound queue using a special transaction.
·        Monitoring the Outbound Queue
If you can send IDocs via qRFC, you can monitor the outbound queue using a special transaction.
·        Active Monitoring
This function provides you with a report that informs you if the number of critical IDocs exceeds a certain threshold.
Active Monitoring Locate the document in its SAP Library structure
Use
This report automatically informs the agents responsible if too many incorrect IDocs are found.
Integration
Active monitoring is not used for processing or reimporting of an incorrect IDoc. Exception handling of every incorrect IDoc is responsible for this.
Activities
You plan the report to run regularly with a variant. The variant also informs the report of the status values to be selected: If the critical status contains more IDocs than specified in the critical number of IDocs, a message is sent to a predefined recipient.
The recipient receives the notification in the form of a work item displayed in their Business Workplace. If they execute the work item, the IDoc statistics are displayed with the values determined at the time of evaluation. The agent can display the current status of these IDocs using the Refresh function. The selection criteria which led to the notification are also used for this evaluation.
Example
An important customer orders goods using EDI on working days, between 8am and 6pm. These goods are to be delivered at 4pm the next day. To ensure that the delivery is made on time, the ordered quantity must be recorded by midday on the day of delivery. The active monitoring function is to be used at 8am every morning to determine whether there are any orders which could not be processed automatically. The report, therefore, is started at the same time every day and 0 is selected as the critical number of IDocs. The agent responsible is notified if any incorrect IDocs are found and can then manually process the outstanding orders by midday.
For more information see
Schedule Monitoring Job (example)
A processing status is assigned to an IDoc during processing (e.g. Status03: Data Transfer to Port OK). These status values are in turn assigned to a higher level status group (e.g. Output: IDoc Transfer Successful). This assignment to a status group is referred to as Qualification. You can change the assignment of status values to status groups in the Edit Status Values transaction.
Procedure
       1.      To edit the status groups, choose the ALE customizing transaction SALE ® Set-Up System Monitoring ® Set-Up IDoc Status Display ® Edit IDoc Status Values (WE47).
A list of statuses which have been defined is displayed.
       2.      If necessary, choose This graphic is explained in the accompanying text. By double-clicking on the status that you wish to assign a different status group, the detail screen is displayed.
       3.      The status group is displayed in the Qualification field. Use the F4 input help for an explanation of the numbers.
       4.      Select Save.
ExampleExample
Status 25 (processing despite syntax error (outbound)) is assigned status group 1 = Outbound: IDoc generated". Replace 1 with 5 for Outbound: IDoc Interface error".
Chek Tcodes in WE02 OR WE05
Regards,
Phani,
Points If Helpful.

Inbound Idoc - permitted agents

In my inbound IDOC my partner profile permitted agents do not get a work item when the IDOC does not post due to some error. I seem to recall that some work needed to be done with the organization structure. Can you point me in the right direction as to which steps I may have missed?
Thanks

Hi Raynald,
Next step is to check with transaction SWETYPV if the type linkage for IDOCAPPL and event INPUTERROROCCURRED has been activated.
If this is the case you will find workitems for this task in the monitor (use transaction SWI2_FREQ) whenever an IDoc with status 51 has arrived for your message type.
Could you please check is the type linkage is active and if so wether or not work items have been created?
Regards,
John.

Workflow to be triggered if Inbound Idoc is successful

Hi,
Kindly help me out with the following senario:
After the vendors are created in MDM, they are distributed to an R/3 (ECC 5.0) system via XI. XI uses the message type CREMAS to distribute the vendors. When the inbound Idoc is successsful, a workflow should be triggered to the concerned user about the vendors created in the R/3 system.
How can we find out which event gets triggered when the Idocs were successful such that we can trigger a custom/standard workflow??
Thanks in advance
Regards
Kishan

This report might help you
RSEIDOCM
Otherwise maybe in ALE customising you could create an event in a user program and use FM SAP_WAPI_START_WORKFLOW to launch your workflow.
You will have the IDOC message types coming in and the process codes which are executed so you should be able to monitor the process and take whatever action you need during the process..
(Customising -- use transaction SALE)
cheers
jimbo

Workitem not triggered for Inbound IDOC Error (ORDERS05)

Hi,
The work item is triggered for the Syntax Error in the Idoc (EDI: Partner profile Not Available).
But, as per my requirement i need to get the idoc error status (as Workitem) , any help regarding the resolution of this issue is highly appreciated.
Regards,
Rusidar S.

Hi Uwe,
Many thanks for your response, well i did run the report name that you said me.. when i executed that report i got a workitem as "ALARM Message from Active IDoc Monitoring" and workitem for EDI syntax errors"EDI: Partner profile inbound not available"
But my objective remains unsolved.. i need the error status of idoc to be generated, do u have any idea or solutions, kindly share it as its the 3rd day that am still into the same task....
Regards,
Rusidar S.

Inbound IDoc must trigger a workflow if shipment already exists

Hi friends, my requirement is that:
I will be getting shipment details via an Inbound IDoc into my SAP system. (IDOC_INPUT_SHPMNT) If the shipment number already exists in the system a workflow error must occur. Also the delivery number in the shipment should be validated for the shipment, if not a workflow notice should generate.
Could someone please help me in doing this.
All helpful answers will be appreciated.
Thank You

This report might help you
RSEIDOCM
Otherwise maybe in ALE customising you could create an event in a user program and use FM SAP_WAPI_START_WORKFLOW to launch your workflow.
You will have the IDOC message types coming in and the process codes which are executed so you should be able to monitor the process and take whatever action you need during the process..
(Customising -- use transaction SALE)
cheers
jimbo

IS Retail:Report/Document generation for inbound IDOC for Cashier Statistic

Hi Friends,
I have generated an inbound IDOC for Cashier Statistics with transaction WPUK in IS retail.
The IDOC is generated successfully which I can view in POS interface monitor with transaction WPER.
But i dont see any corresponding report or document generated for this successfully posted IDOC.
Is there a functionality in IS retail to generate report/document for successfully posted IDOC for cashier statistics?
Request you valuable inputs on this please.
Regards,
Debraj

Hi John,
Thanks for your inputs.
Could you please let me know how do i activate infostructure S122 to see reports related to cashier statistics after successful posting of IDOC?
Regards,
Debraj

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).

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

How to read file from prsntn server in Inbound idoc FM.

Hi Experts,
I am new to idoc.
I have requirment that i need to read a file from presentation and application server and put in inbound idoc FM.Idoc will be processed in batch.
How can i put selection screen in FM and read the file?or how can i proceed with the solution?
Please help..
Umesh

Hi Umesh,
My understanding on your requirement is to read a file from pres. server and pass the data to an IDoc function module. Am I correct?
If this is the case then you can create a report which picks up the file from pres. server and then read data from the file and pass it to the parameters of the required function module.
Hope this helps.
Regards,
-Sandeep

Inbound idoc monitoring

Similar Messages

Maybe you are looking for