Help in IDOC Processing

Hi friends,
I am getting inbound idoc from Biztalk which posts a sales order in SAP. now i am getting the following error
Field RV02P-KUNDE (1) is not an input field
this is Sold-to Party field in Sales order header data.
when processing the idoc frm we19 in forground mode, i am getting the warning message and after pressing enter Sales order posted successfully. But in background processing its giving an error. Now i want to by pass this warning message. how to do it ? can any body help me on this ? which user exit should i modify ?
Thanks in Advance.
Regards,
Joseph

Hi Srikanth,
Thanks for the reply.
the field KUAGV-KUNNR is in header data sold to party. I am not talking about that.
In Sales order header data, Go to Partners tab, there in the first place you will have Partner function and partner number know, there i am getting my error.
Can you help me to solve this issue ?

Similar Messages

Uregnt help on IDOC Processing

Hi,
can anybody xplain how to solve the following scenario.the scenario is "look at number of records transferred and number of records added in the BW cube compare to IDoc record number.All IDocs should be status 53."

Hi Ram,
you can get the number of records transferred and added to a cube from its maintenance screen. right click on the cube and go to menage. In the request, you can find these figures. Comparing the idoc record numbers can be done using the transaction BD87. Hope this helps.
Thanks and Regards
Subray Hegde

Creation of rfilr ports in WE21 from LSMW IDOC Processing

Hi,
I am trying to defile a file port for INBOUND IDOC processing status in LSMW.
Now when I go to create a file port in WE21, I give some dummy Physical directory name. But what should I give in
Function module field and Outbound file field ? Is it compulsary to put something in these fields...
Please help.....

Hi,
Function module field is used to define the path functionality of file generated.
EDI_PATH_CREATE_CLIENT_DOCNUM is the recommned fucntion by SAP .
Function is used to prevent unprocessed files being overwritten.Tihs function generates file directory path dynamically.
Hope this helps.
Thanks.
Mark points if helpful.

Tax with the help of idoc and EDI

Dear gurus,
how can we process tax data that is used between two systems through the help of IDOC and EdI? It would be great for ur kind support.

Hi Amit,
I do not understand how a non-sap system having an idoc adapte?
Do you mean the non-sap system has the ability to understand the IDOC files?
If yes, then your scenario is typically a IDOC-to File scenario.
Read this:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
If you do not intend to use XI in between, then you can just configure the outbound IDOCs in your SAP system and configure a file port in we21 transaction and create the partner profile in we20 transaction.
Regards,
Ravi

IDOC process in QM

Hi,
Can any one help me to understand the use of IDOC Process in QM???
In which scenarios we will use IDOC in QM.

Hi,
May be this link will help you.
http://scn.sap.com/thread/171671
sandip

Basic doubts in ALE/IDOC processing

Hi All,
1.How are IDOC Type and Message Type related? Many to one or One to Many?
2. what is the prominence of msg code and msg function in ALE outbound processing?
3. During outbound processing what is the startegy followed by the ALE service layer to pick up the customer model?
It would be great if any one can answer these questions in plain words rather than referring links. Reward guaranteed.

Hi Ravi,
1.Can'te we assign more than one IDOC to the same msg type if the IDOC's are of different versions?
Yes we can. Doesn't SAP do that? For example, ORDERS01, ORDERS02 ... ORDERS05 are having the same message type ORDERS. You can also create your own IDoc type or extend the standard IDoc type.
3. When we run a stand alone program to trigger IDOC processing the only mandatory field will be the message type, so how can the sending system identify the receiving system?
You need to setup partner profile (t/code WE20) and distribution model (t/code BD64). Once this configuration are done, The system will populate automatically the IDoc Control Record for sender and recepient system information when the IDoc generated based partner profile setup.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Inbound idoc processing by workflow

Hello,
How can I find if an inbound IDoc has been processed via workflow ?
following are details -
1)status records 50 and 64 for the idoc show RFC user ID whereas 62 and 53 show WORKFLOW_020 user ID.
2)manual re process in test system using WE19 has all four status records by login user ID.
3)BD67 values for this process code was checked for the start events.
4)I checked standard task 30200090 following oss note 325361
5)The invoice document posted via this idoc has created by user ID as WORKFLOW_020
I do not have full knowledge of inbound idoc processing via workflow and I am in the process of learning the same. Kindly help.
thank you very much in advance,
Bhakti

Hello,
How can I find if an inbound IDoc has been processed via workflow ?
following are details -
1)status records 50 and 64 for the idoc show RFC user ID whereas 62 and 53 show WORKFLOW_020 user ID.
2)manual re process in test system using WE19 has all four status records by login user ID.
3)BD67 values for this process code was checked for the start events.
4)I checked standard task 30200090 following oss note 325361
5)The invoice document posted via this idoc has created by user ID as WORKFLOW_020
I do not have full knowledge of inbound idoc processing via workflow and I am in the process of learning the same. Kindly help.
thank you very much in advance,
Bhakti

Inbound Idoc processing issues - Partner Profiles - error status 56

Hello All,
I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?
SOAP Header in IDocOutbound tag
<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
<SAP:RCVPRN>[String Value]</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?
When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
Any help is very much appreciated! :-D

Hi Jason ,
Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select Create New button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in XI towards R/3
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Inbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
do let me know if it helped
Edited by: Tom Jose on Feb 21, 2008 9:04 AM

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.

How to control IDOC processing in XI

hi
I have scenario where File --> XI --> IDOC
Source structure
Header           1...1
    Detail         0..unbounded
Trailer             1..1
For every detail i need to generate 1 doc
My requirement is that i dont want to send all the IDOCs at one shot from XI.
trfc connection should be open just once for all the IDOCs and not single IDOCs are posted.
Is there any transaction from where i can control my IDOC processing.
Need urgent help.
Thanks ,
Loveena

Hi Loveena,
in a scenario, for instance, where you send IDOCs of type LS (logical system):
1. In the sender system, call transaction WE05 to display the outbound IDoc. The IDoc partner type of both receiver and sender is LS.
2. On the Integration Server, call transaction SXMB_MONI (Integration Engine Monitoring Monitor for Processed XML Messages) to display the message.
3. In the receiver system, call transaction WE05 to display the inbound IDoc.
if it helpful reward points are appreciated

IDoc Processing in SAP

Hi Team,
I have question about SAP Idoc processing ,
1) How does SAP process Idocs when it gets around 20 Idocs all in a fraction of secodes for same Idoc/process code and message type . Will SAP process them one by one , or it will process them all together in parallel processing. Please help me out with this.
2) We have SAP 3.1 released used for creating delivery when an Inbound Idoc get in to SAP. Most of the time we see Idocs creating delivery but some time Idocs does not create delivery in production, we never had this issue in quality. What can be probale cause of this isse?
3) We are facing a strange problem , We have one Inbound Idoc which perform following activity :
1.       Change delivery (Already created Delivery )
2.       MB1C (add Inventory )
3.       Picking
4.       PGI
In the above flow next step will be executed only when preceding steps is successful .Every process is doing itu2019s job in Test /Quality /Production system as expected . But in production some time we are getting some problem while performing Change delivery / Picking . I would like to know from you people have you ever came across such scenario or you have something to add to the process then please share the approach to minimizes the cause.
Please share your views.
Thanks,
Raj

Hi,
The no of IDocs processed at a time is based on the Packet Size that is specified in the configuration of the Partner Profile(WE20). Likewise the specification of the Output Mode is given as either Transfer IDocs Immediately or Collect IDocs in which case the IDoc would go to 30 status and it would have to be processed using RSEOUT00.
Thanks
Krithika

Essential Transfer Parameters Missing in record during Inbound IDOC process

Dear Gurus
We are creating a Inbound delivery in one system, we have made all the custom settings for IDOC processing for inbound and outbound idoc in both the systems. Upon the execution of inbound delivery, the system
During the Inound delivery processing, the outbound IDOC is successfully distributed. However in the receving system, the IDOC is not posted and it throws the below erroe\r
Essential transfer parameters are missing in record: 0180000055 000010 / Mess number 561 and message type E
We are using Outbound IDOC mess type DESADV basic type DELVRY01 process code DELV with FM IDOC_OUT PUT_DELVRY
In the receiving system message type DESADV , process code DELS, and FM IDOC_INPUT_DESADV1
What is that which is going wrong.
Please help me out
Thanks

Hello
To create inbound delivery from outbound delivery, use following setting -
Outbound idoc -
idoc type - DESADV01
message type - DESADV
Process code - SD05
FM - IDOC_OUTPUT_DESADV01
Inbound iDOC -
Message Type - DESADV
Process Code - DESA
FM - IDOC_INPUT_DESADV
Idoc Type - DESADV01

Idoc processing best practices - use of RBDAPP01 and RBDMANI2

We are having performance problems in the processing of inbound idocs. The message type is SHPCON, and transaction volume is very high. I am a functional consultant, not an ABAP developer, but will try my best to explain our current setup.
1)     We have a number of message variants for the inbound SHPCON message, almost all of which are set to trigger immediately upon receipt under the Processing by Function Module setting.
2)      For messages that fail to process on the first try, we have a batch job running frequently using RBDMANI2.
We are having some instances of the RBDMANI2 almost every day which get stuck running for a very long period of time. We frequently have multiple SHPCON idocs coming in containing the same material number, and frequently have idocs fail because the material in the idoc has become locked. Once the stuck batch job is cancelled and the job starts running again normally, the materials unlock and the failed idocs begin processing. The variant for the RBDMANI2 batch job is currently set with a packet size of 1 and without parallel processing enabled.
I am trying to determine the best practice for processing inbound idocs such as this for maximum performance in a very high volume system. I know that RBDAPP01 processes idocs in status 64 and 66, and RBDMANI2 is used to reprocess idocs in all statuses. I have been told that setting the messages to trigger immediately in WE20 can result in poor performance. So I am wondering if the best practice is to:
1)     Set messages in WE20 to Trigger by background program
2)     Have a batch job running RBDAPP01 to process inbound idocs waiting in status 64
3)     Have a periodic batch job running RBDMANI2 to try and clean up any failed messages that can be processed
I would be grateful if somebody more knowledgeable than myself on this can confirm the best practice for this process and comment on the correct packet size in the program variant and whether or not parallel processing is desirable. Because of the material locking issue, I felt that parallel processing was not desirable and may actually increase the material locking problem. I would welcome any comments.
This appeared to be the correct area for this discussion based upon other discussions. If this is not the correct area for this discussion, then I would be grateful if the moderator could re-assign this discussion to the correct area (if possible) or let me know the best place to post it. Thank you for your help.

Hi Bob,
Not sure if there is an official best practice, but the note 1333417 - Performance problems when processing IDocs immediately does state that for the high volume the immediate processing is not a good option.
I'm hoping that for SHPCON there is no dependency in the IDoc processing (i.e. it's not important if they're processed in the same sequence or not), otherwise it'd add another complexity level.
In the past for the high volume IDoc processing we scheduled a background job with RBDAPP01 (with parallel processing) and RBDMANIN as a second step in the same job to re-process the IDocs with errors due to locking issues. RBDMANI2 has a parallel processing option, but it was not needed in our case (actually we specifically wouldn't want to parallel-process the errors to avoid running into a lock issue again). In short, your steps 1-3 are correct but 2 and 3 should rather be in the same job.
Also I believe we had a designated server for the background jobs, which helped with the resource availability.
As a side note, you might want to confirm that the performance issues are caused only by the high volume. An ABAPer or a Basis admin should be able to run a performance trace. There might be an inefficiency in the process that could be adding to the performance issue as well.
Hope this helps.

IDOC process

gud mrng,
after creating the idoc function module,how are we writing the code?
how are we using the standard idoc?

Hi Priya ,
Check this .....
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
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.
Reward if useful.
Regards,
Chitra

Cancel a Sales Order via IDOC processing

Hello,
I am trying to cancel an item within a sales order using ORDERS05 (IDOC_INPUT_ORDCHG).
My IDOC contains the following data:
E1EDK01-ACTION = 003 (Changes in one or more items)
E1EDK02-QUALF = 002 (Vendor Order)
E1EDK02-BELNR = SAP Sales Order Number to be updated.
E1EDP01-POSEX = SAP Sales Order Item Number to be deleted (eg. 000010).
E1EDP01-ACTION = 003 (Item cancelled)
E1EDP19-QUALF = 002 (Material number used by vendor)
E1EDP19-IDTNR = SAP Material Number of Item to be deleted
However it does not seem to be working correctly. Instead of removing the item from the sales order - it actually creates a new item.
Has anyone had any experience with successfully cancelling an item using IDOC processing?
Any assistance would be greatly appreciated.
Thanks and Regards,
Corinne

Hi Corinne,
I don't think you'll get back the response you want from SAP. This idoc was originally created to support the EDI scenario where your customer makes a change to their purchase order. The EDI message would be sent to SAP to update the corresponding sales order in your system (after being mapped to an Idoc).
As your customer does not normally not have your sales order item number in their system, they can only send their own purchase order item number. SAP then uses this number to look up the corresponding SAP sales order item number via the VBAP-POSEX field (which in this scenario is originally populated by the Idoc which created the order from the customers original purchase order EDI message).
So, I dont think SAP will change this functionality. They may offer, however, a work around!
What I still think is strange though, is that, having not found a match for your item on the POSEX field, SAP ignores the deletion flag and adds a new item to your order. At the very least you would expect it to just ignore the item (a quick look at the code in 4.7 seems to imply that this is what SAP is trying to do - maybe a change from your version?).
Hope that helps.
Brad

Help in IDOC Processing

Similar Messages

Maybe you are looking for