Flag for IDoc processing in VA01

Is there a flag I can check within userexits in transaction VA01, which shows me, wheter an sales order is created via IDoc processing?
I must differ between IDoc and normal BTCI processing, so sy-binpt or sy-batch can n ot be used.
thanks for your help,
Axel

Hi Axel,
Actually in most of the scenarios the id with which a idocs are being triggered from a remote system based on the RFC call will be different. I mean there will be a different user id's for batch programs, or rfc programs etc. Based on the is you can identify if the document is created via a idoc.
In VBAK there is ERNAM field if its created in online mode by a user it will have the user name and if its created by a specific user id like WFBATCH or some thing simialr you can identify the document is created via either IDOC or some other applications.
In some cases companies also misuse any other field from VBAK which they dont use to set a flag to identify if the document is created via Idoc.
Hope this helps
Cheers
VJ

Similar Messages

Batch job for IDOC processing in 64 status

Hi experts ,
i want to know the name of Batch job for IDOC processing in 64 status.
I have configured the partner profiles as 'process immediatly'.
So with this configuration whenever an idoc comes in production it gets processed immediatly and automatically.
i want to know how they are getting processed automatically.
is there any job which looks for these idocs(in 64 status and process immediatly flag) and process it.
What is the trigger for thiese idocs processing???
Please guide me
thanks in advance
Anit gautam

Hi Thanks for ur reply.
=====Upon arrival, "process immediately" should fire that process =====
how it is getting fire?
means is there any batch job running which looks for idoc in 64 status or is there any event which get triggered when an idoc
comes in 64 status.
why we use OYEB transaction???
Regards

Function module creation for IDOC processing...

hi Experts,
             i want to create a function module for idoc processing..
message type: zashpmnt
idoc type : shpmnt05
plz tell me which standard FM is used... and tell me what changes i want to do in it....
Tnx in Advance..

Hello,
         If you are trying to process an Outbound IDoc for the SHIPMNT05 IDoc Type with an Extension, you can use the IDOC_OUTPUT_SHPMNT Function Module which is assigned to SHPM Process Code.
       In Addition, since you have an IDoc Extension, you are required to populate the Custom Segment / Fields. For this, there is a Customer Function / Exit called EXIT_SAPLV56K_002 which you can use it for adding your Custom Segments to the IDoc ZSHPMNT05.
       If you are writing code in this exit, make sure to create a Project in CMOD.
       Also, ensure that you've made the assignment in WE82 with the Message Type , IDoc Type & the Extension.
       For Inbound, if you would like to Create a Custom Function Module, you can follow the Naming Convention Z_IDOC_INPUT_SHPMNT for which you are required follow the below Steps.
1. Register the FM as Inbound FM in BD51 T-Code.
2. Assign the FM to IDoc Type & Extension in WE57.
3. You'll need to Create a Custom Process Code in WE42 in which you are required to make add your FM.
4. Maintain Partner Profiles in WE20.
5. Have the Process Code Migrated to the Testing Environment as creation of Custom Process Code is a Customizing Activity and it requires a Customizing Request to be created / Migrated.
6. Define the Parameters as defined in the Standard Inbound Function Modules such as IDOC_INPUT_ORDERS , IDOC_INPUT_DELVRY etc.
Thanks and Regards,
Venkat Phani Prasad K

RBDAP001 causing a short dump when submitted in a FM for IDOC processing

Hi All Gurus,
I have a situation wherein I need to automate the processing of failed INBOUND IDOCS.
So the status of failed IDOCS could be 51 or 64 or anything like that.
I tried using statement 'SUBMIT RBDAP001 with......'. in a custom FM , however I got a short dump.
When I debugged I realised that RBDAP001 pops up a screen with the final IDOC processing result which probably may be the cause of dump. Dump message is 'CNTL_ERROR'.
So is there a way how I can suppress this screen OR use any other function module to process these inbound Idocs.
Appreciate your advise on same.
Thanks and Regards
RK

Hi Rajiv,
Please use program RBDMANI2 to reprocess IDoc with status 51.
Also check program RBDINPUT for reprocessing IDoc with other statuses.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

BAdi for IDOC processing

Hi,
I am working on the CRM 5.0.
Any one worked on the BAdi "CMS_IDOC_BADI" (CMS BADI for IDOC related processing) for populating the custom fileds in the IDOC.
Pls let me know.
Thanks.
Rohita.

Hi,
I have the structure CMST_CDT.
I need to modify this structure.
There are some custom fileds in the ITEMS.
CMST_CDT_ITEM_XT---CMST_CDT_ITEM_TAB---CMST_CDT_ITEM.
In CMST_CDT_ITEM we have ITEM_EXTN.
I need to modify some fileds in this ITEM_EXTN.
Could any one pls help me in this ?
Thanks.
Rohita.

Settings for IDoc Processing Maintain Partner Profile Manually

Hi Everybody,
I just wanted to maintain a partner profile for IDoc Outbound Processing in CRM7.0. The Partner Type is LS (Logical System).
Now, when I'm creating an Outbound Parameter and want to save, I get an Error Message that the field package size must be > 0.
The problem is, that there is no field Package Size. In older systems there is such a field under the field receiver port.
Anyone any idea where is the missing field or another solution.
Thanks and regards,
Sebastian
PROBLEM SOLVED !!
When you get the error message, press enter several times and the field appears. Incredible.... but true.
Edited by: Sebastian Wilhelm on Sep 3, 2009 4:06 PM

Hi,
Steps to do ALE Configuration with respect to IDOC:
Configuration in R/3:
1. Create a RFC destination using Transaction = SM59
2. Create the ports using we21 and refer the port to the created RFC dest in above Step.
3. Create a Logical System using Transaction BD54.
4. Create a partner profile using transaction WE20.
Also need to configure in XI:
1. Create a RFC destination using Transaction = SM59
2. Create the ports using Transaction IDX1 and refer the port to the created RFC dest in above Step.
3. The port has to be displayed in the IDX2 transaction and we should be able to view the idocs which we imported through integration repository otherwise we have to manually import the idocs from IDX2 using the port created above
Also refer to the link below for further details:
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Regards,
Nithiyanandam

We 19 rest tool for idoc processing

hi to all abap gurus
i heard that we19 is test tool for idoc proceesing and it is also also used for idoc deletion .
may i know what is idoc testing why it is required . can u pls explain n in detail ?
and so many options are there in we19 tcode like inbound function module .
and tell me how to create idoc dynamically and send to the other system by using we 19 tool
thanksssss in adavance

Intermediate Document
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. IDoc is not a process.
-         IDocs are stored in the database.
-         In the SAP system, IDocs are stored in database tables.
-         IDocs are independent of the sending and receiving systems.
-         IDocs are independent of the direction of data exchange.
Creation of IDOCs
?         Transaction code: WE 30
Defining Segment:
Creating Segment : Tcode - WE31
Creating Message Type : Tcode - we81
Assigning Message type to Idoc type: Tcode - we82
Process
The two processes for IDoc are Outbound Process and Inbound Process.
Outbound Process
When the data is sent out from the system, the process is called Outbound Process and the IDoc is known as Outbound IDoc.
Inbound Process
When the data is coming in, the process is called Inbound Process and the IDoc is known as Inbound IDoc.
Outbound Process (Sending System) Steps :
1) Goto Tcode SALE:
Click on Sending & Receiving Systems à Select Logical Systems
Here Define the Logical Systems à Click on Execute Button
Go for New Entries
1)       System Name : LOG1
Description: Sending System
2)       System Name : LOG2
Description: Receiving System
Press Enter & Save it will ask for Request if you want new request create new request or press continue for transferring the objects.
Assigning Client to the Logical System:
Select Assign Client to Logical Systems -à Execute
Ø      100 à Double click on this and give the following information
           Client                   : Sending System
           City                      : Chennai
           Logical System    : LOG1
            Currency                   :
            Client role                  :
Ø      250 à Double click on this and give the following information
Client                     : Receiving System
City                        :
Logical System    : LOG2
Save this Data.
Step 2) For RFC Creation:
-         Goto Tcode SM59 à Select R/3 Connects
Click on create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
Give the information for required fields:
RFC Destination    : LOG2
Connection type     : 3
Target Host              : sappdc.wipro.com
System No              : 00
Client                       : 210
User                            : Login user name
Password                   :
Save this & Test it and Remote Login
Step 3) Goto Tcode BD64: - Click on the change button
Click on the create model view
Short Text: model view
Technical Name: LMOD
Save this & press ok
Select just created model view
Name: "LMOD"
Goto add message type
Model Name : LMOD
Sender           : LOG1
Receiver          : LOG2
Message type: ZAZHARMESS
Save and press Enter.
4) Goto Tcode BD82:
Give Model View   : LMOD
Partner system      : LOG2
Execute this by pressing F8
It will gives you sending system port No: A00000000089 (Like)
5) Goto Tcode BD64:
Select the model view
Goto à Edit à model view à Distribute
Press ok & Press Enter.
Run your Zprogram
REPORT ZIDOC1                             .
DATA: Begin of imara occurs 0,
matnr like mara-matnr,
mtart like mara-mtart,
end of imara.
DATA: wamas_con LIKE edidc,
imas_data LIKE edidd OCCURS 0 WITH HEADER LINE,
icom_con LIKE edidc OCCURS 0 WITH HEADER LINE.
PARAMETERS: e_matnr LIKE mara-matnr,
e_msgtyp LIKE edidc-mestyp,
e_rcvprn LIKE edidc-rcvprn.
retrive app. data from DB
SELECT matnr mtart FROM mara INTO TABLE imara WHERE
matnr = e_matnr.
*Master idoc control record
wamas_con-rcvprt = 'LS'.
wamas_con-rcvprn = e_rcvprn.
wamas_con-idoctp = 'ZAZHARIDOC'.
wamas_con-mestyp = e_msgtyp.
master idoc data records
LOOP AT imara.
imas_data-segnam = 'ZAZHARSEG'.
move imara to imas_data-sdata .
APPEND imas_data.
ENDLOOP.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
EXPORTING
master_idoc_control = wamas_con
TABLES
communication_idoc_control = icom_con
master_idoc_data = imas_data
COMMIT WORK.
6) Verifying Transfer of IDOCs Tcode - we05
ALE/IDOC Status Codes (outbound):
01    à IDoc Added
30 à IDoc ready for dispatch
29 à Error in ALE service Layer
12 à Dispatch ok
      03 à Data passed to port ok.
Inbound Process (Receiving System) Steps:
Do the same step as you did in sending system
ü      Creating IDoc
ü      Defining the Segment
ü      Creating Message Type
ü      Assigning the Message Type
ü      Defining the Logical System
ü      Assigning the Logical System
ü      Creating the Distribution Model
Goto Tcode - we57:
Assign function module to IDoc type
Module: Function module
Basic type:
Message type:
Direction: 2 (inbound)
Creating Inbound process code - we42
Verifying Idoc List Tcode - we05
ALE/IDOC Status Codes (Inbound):
50 à IDoc Added
51 à Application Document not posted
64 à IDoc ready to be transferred to application
62 à IDoc passed to application
53 à Application Document posted
Useful transactions for IDocs
BD87 : Status Monitor for ALE Messages
SALE : Display ALE Customizing
WE02 : Display IDoc
WE05 : IDoc Lists
WE09 : Search for IDoc in Database
WE19 : Test tool
Check this link,
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/step%2bby%2bstep%2bprocedure%2bfor%2bcreation%2bof%2bidoc

Background JOB scheduling for BD87 transaction for IDOC processing

Hello All,
I have a requirement to schedule program(BD87) for background processing.I have created varient for selection screen.
Query is how do i slect a particular node ithe tree and execute a particular button in background processing.
Do i need to write BDC for BD87 transaction?? or there is any other approach for the same.
Thanks.

oh!! that's different! if your IDOCs have errors and remain in status 51, no transaction in the whole world can proceed them.
you will have to investigate what caused the status 51. go to transaction BD87, select your IDOCs and go to the IDOC-body. you have several segments there: contol, data and status ... go to the status-segment, open it and double-click on the message in red at the side of the status 51 - analyse the error, edit the IDOCs or - if that is no solution, kill them and create new ones.
what is the error message? (just out of curiosity ...)

Problem with WE19 Test tool for idoc process

Hi,
I have a idoc in 51 status. This idoc is used for order creation and its an inbound idoc.
This idoc has around 2000 line items. On checking the status for this idoc, i find that in a particular line item(223) error is showing.
So in WE19, I entered this idoc no. and deleted all the line items below the error line item. Now when I click on 'Standard Inbound', I am getting error mssg 'Receipient port invalid', 'idoc was saved but cannot/ should not be processed'.
How to correct this. After this idoc is processed and generates a sales order, I want to insert the error line item and find the issue.
Please help.
Thanks & Regards,
Hari Om

Hi,
Receipient port invalid You must have taken the IDOC from Production and put it in the development or quality I guess.That is why system gives this error.
To solve this issue Click on edit control record fields that is first line. Change the port for the reciepient for example change it from SAPproduction to SAP development /SAP quality
Incase of further queries please reply
Regards
Mano

ALE Settings for IDOC Processing

Hi,
Can anybody tell me what all the ALE settings I have to look for any IDOC.
Thanks,
bsv.

Hi,
Please check this link for ALE setup for inbound and outbound processes.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
Regards,
Ferry Lianto

WE19 - Test tool for IDOC processing

Hi:
As we know WE19 is the test tool, and it has downside that it translates everything into upper case.
Even SAP has a note for it, stating that it is not going to change. but it gets changed everything in upper case .
In Our requirement; some fields` value in lower case (or partially lower case) are required by using this tool, it converts these into upper case and hence our process does get failed.
Let me know if any exit or bapi or some other solution for it.
<REMOVED BY MODERATOR>
Thanks in advance.
Regards
Shashi
Edited by: Alvaro Tejada Galindo on Apr 22, 2008 4:07 PM

Hi,
Do I understand that correct that SAP says in a note that the data will not be converted to upper case in WE19, but it is getting converted anyway?
In this case I would definitely raise an OSS message because according to SAP WE19 is not supposed to change the entries into upper case.
If I misunderstood your comment then the only possibility would be to hook into one of the user exits. Every IDOC that is created uses a function module that processes the IDOC and passes the data to the application. The user exit you can use depends on which IDOC type you are using. The import function modules start with IDOC_INPUT_*. Once you find out which function is used just look into the coding to identify the user exits. Use an exit at the beginning to convert the data before it is passed to the application.
Hope that helps,
Michael

Reports for IDOC processing

hi there,
can u please let me know the use of reports
RBDMANIN, RBDMANI2, RBDAPP01, RBDMON00

hi,
the programs RBDMANIN, RBDMANI2 are used to process the error idocs. RBDAPP01 is to process the Idocs which are ready for transfer. and the last RBDMON00 is to choose the Idocs to process . some of the programs are documented just check it.
Regards
vijay

Inbound file for IDOC processing

Hi SAP Gurus,
I want to create an IDOC by using INBOUND FILE option in WE19. Can anybody suggest, how the flat file will look like ?
FYI, my Idoc type is BBP_PCSTAT01 ( Procurement Card Statement).
Any idea ?
Thanks and Warm Regards.
Pras Durafe

This is an example of idoc with flat-file:
EDI_DC40 100000000000413988546B 2 INVOIC01 INVOIC MM E97A INVOICSNDPRN LIRS86092747 SAPITZ LS CLNTITZ100 20040210105203
E2EDK01005 100000000000413988500000000000001 USD INVO4139885
The first record indicate the header data; after this, for each segment type, the information about the segment.
If you send me your email address, I can send you a complete example file.
Gianluca

Test tool for IDOC processing issue

Hi
I am doing a IDOC to File Scenario
Please clarify me
The RFC destination and Port which I have created in ECC I am getting the same in the "Edit Control Record Fields Receiver Tab"
But
The RFC destination and Port I have created in XI is not appearing in the "Edit Control Record Fields Sender Tab" (when I pressF4)
where I should have to check for this errors.
Please check this link
http://www.flickr.com/photos/33169400@N05/3097589223/
thanks
manian

Thanks Creasy for your reply
Actually I am following the below link.
Pls refer Step4 Page 6. He has selected tRFC
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/soa-middleware/soa-management/exchange-infrastructure/a%20step-by-step%20guide%20on%20idoc-to-file%20using%20business%20service%20in%20the%20exchange%20infrastructure%20integration%20directory.pdf
thanks
manian

Filter conditions for Standard Idoc processing

Hi Experts,
       In BD64 - Distribution model , I have created filters for MATMAS based on Division, Sales Organization, Distribution channel and Material Type.
when I process the IDoc through BD10 - Send material it is not getting filtered based on the conditions set in BD64.
eg) I have created a material in a particular sales organization for which the data should not be processed through Idoc based on the filter condition set for sales org in BD64.
   But now that the condition is not been checked and the Idoc is processed when i send it through BD10.
whether BD10 will not check for the filter conditions?

hi asik,
partner in the generated idoc and in BD64 as a Receiver are the same.
I am using single filter group in BD64 ( Matmas ) for Division , Sales Org, Distribution channel and material type.
The filter group comprises the following filters:
Division                             - 01
Division                             - 02
Sale org                            - ABCD
Sale org                            - EFGH
Distribution channel          - AA
Distribution channel          - BB
Mtrl Type                          - SPAR
Mtrl Type                          - FNGD
These result in the filter conditions should be like
(Division 01 OR division 02)
and
(sale org ABCD or EFGH)
and
(Dst Channel AA or BB)
and
(mtrl type    SPAR or FNGD )
Scenario for idoc processing
                                         Division          01
                                         sale org         xxxx
                                         dst channel   AA
                                         mtrl type        FNGD
the Idoc should not be processed for the above scenario
but its triggering an Idoc when I test it through BD10.

Flag for IDoc processing in VA01

Similar Messages

Maybe you are looking for