Background Idoc processing

Hi,
I just wanted to know what is process code and why it is needed for IDoc processing?
Is there any possiblity by which IDoc can be processed background and if any then how?
Thanks
Parag

Hi Parag,
Pls refer below links to know more about your qurey.
[http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b804043d711d1893e0000e8323c4f/frameset.htm]
[http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm]
Regards,
Sanjit

Similar Messages

Scheduling inbound and outbound idoc processing

Hi everybody.
I ´d ike to know which is the best way to schecule the outbound and inbound idoc process.
Nowadays we are using this:
INBOUND PROCESSING
- In WE20 the idocs are checked with "Trigger with a background program".
- The program RBDAPP01 is scheduled with a job to trigger the process of the inbound idocs.
OUTBOUND PROCESSING
- The program RBDMIDOC is scheduled to create the idocs than have been created with change pointers.
- The program RSEOUT00 is scheduled with a job to trigger the process of the outbound idocs.
Is there any better option to improve de perfomance????
Edited by: Christian Abad Chico on Nov 13, 2009 10:09 AM

Any answer

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

Idoc process screen

Hi all,
I am working on an IDOC process that will list the idocs in error which are ready for reprocessing. when I execute this custom transaction it will give me the list of all the idoc numbers with status E i.e. error, when i fix the error and want to reprocess the error it shows me a screen which says
Reprocess Idoc's
and it says "Call Transaction processing" with following radio buttons:
1. In background
2. In foreground
3. In foreground after error.
My functional folk wants to set this radio button as default to In the foreground, so can you please tell me how I can acheive this.
Thanks,
Rajeev

when i process the idoc the start time screen shows after job,after event,at operation mode
does its easy to process the idoc by using this methods and also to schedule.

Trx.: WLF_IDOC - IDoc Processing

Hallo together,
I've a question regarding the transaction WLF_IDOC - Idoc processing.
It should be possible to edit an Idoc, for example an idoc with status 51.
If i mark an entry and press icon EDIT IDOC I get a new screen with the detail information of the idoc, but
it is not possible to edit any field. All fields are blocked.
Thanks in advance for your feedback.
Best regards
Frank

Hi Frank,
There is no WLF_IDOC transaction that exists and not sure which one you are referring to.
However you can go to WLFEIR transaction and provide the idoc number,wherein you will have the following options
1.Change Control Record
2.Change Status
3.Change View - This will take you to WE02 and you can change/edit any relevant segment and then save and then come back to initial screen and process it Online/using B87 or even in background
PS : There are also other options like sending idoc using RFC and comparison of idocs etc.
Hope it helps,
Best Regards,
Aram.

Background schedule process

Hi
I am new to Oracle 9iAS. Can someone tell me if there is any
better way to implement a background scheduled process ?
Currently, I am doing it via AT command. Just wondering if
Oracle9iAS has any scheduler that I can make use of.
Thanks
CT

You can set up the different step while schedule the back ground job. Each step will have the program name, variant.
You can do his using transaction SM36 -> JOB WIZARD.
Thanks,
Srinivas

Error occurs in background work process.

Respected Guru's,
error occurs in two background work process, i have displayed the trace files of both the bgd work process.
How to rectify this error ?
Further, can you please help me in identifying the problem, please suggest me good material which gives steps for troubleshooting such error in the developer's and system trace.
Thank you.
Dayanandan.a
Developer trace file for BGD WP 1
trc file: "dev_w12", trc level: 1, release: "620"
ACTIVE TRACE LEVEL           1
ACTIVE TRACE COMPONENTS      all, M
M systemid   560 (PC with Windows NT)
M relno      6200
M patchlevel 0
M patchno    251
M intno      20020600
M pid        2864
M
M ***LOG Q0Q=> tskh_init, WPStart (Workproc12 2864) [dpxxdisp.c   1016]
M <EsNT> Memory Reset enabled as NT default
M calling db_connect ...
M db_connect o.k.
M rdisp/reinitialize_code_page -> 0
M
M Tue Jul 30 10:22:53 2002
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020730.AUD
M
M Tue Jul 30 10:22:55 2002
M *** ERROR => SlicLockSema: sema locked [slicshm.c    89]
M *** ERROR => SlicShmInit: SlicLockSema failed [slicshm.c    231]
M *** ERROR => SlicValBufInit: cannot initialize SHM [slicshm.c    299]
M *** ERROR => SlicValBufRead: license buffer not initialized [slicshm.c    329]
M *** ERROR => SlicCheckBuf: some error reading license buffer contents [slicshm.c    419]
M
M Wed Jul 31 00:00:49 2002
M SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020730.AUD
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020731.AUD
M Thu Aug 01 00:00:49 2002
M SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020731.AUD
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020801.AUD
M
M Fri Aug 02 00:00:49 2002
M SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020801.AUD
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020802.AUD
M
M Fri Aug 02 00:14:09 2002
M *** ERROR => ThCallHooks: event handler rsts_before_commit for event BEFORE_COMMIT failed [thxxtool3.c 235]
M ***LOG R38=> ThICommit3, db_commit98 ( 001024) [thxxhead.c   10641]
M ***LOG R18=> ThPrivCommit, ThICommit () [thxxhead.c   11307]
M in_ThErrHandle: 1
M *** ERROR => ThPrivCommit: ThICommit (step 4, th_errno 9, action 2, level 1) [thxxhead.c   8277]
M
M Info for wp 12
M
M    stat = 4
M    reqtype = 4
M    act_reqtype = 4
M    tid = 12
M    mode = 0
M    len = 24
M    rq_id = 6638
M    rq_source = 1
M    last_tid = 12
M    last_mode = 0
M    rfc_req = 0
M    report = >                                        <
M    action = 16
M    tab_name = >                              <
M
M
M Modeinfo for User T12/M0
M
M    tm state = 2
M    uid = 13
M    term type = 0x0
M    display = 0x0
M    cpic_no = 0
M    cpic_idx = -1
M    usr = >SAPUSER     <
M    terminal = >                    <
M    client = >800<
M    conversation_ID = >        <
M    appc_tm_conv_idx = -1
M    imode = 3
M    mode state = 0x42
M    th_errno = 9
M    async_receives = 0
M    cpic_receive = 0
M    em handle = 2
M    roll state = 4
M    abap state = 4
M    em state = 3
M    eg state = 1
M    lock = 0
Developer's trace file for BGD WP 2
trc file: "dev_w13", trc level: 1, release: "620"
ACTIVE TRACE LEVEL           1
ACTIVE TRACE COMPONENTS      all, M
M systemid   560 (PC with Windows NT)
M relno      6200
M patchlevel 0
M patchno    251
M intno      20020600
M pid        2872
M
M ***LOG Q0Q=> tskh_init, WPStart (Workproc13 2872) [dpxxdisp.c   1016]
M <EsNT> Memory Reset enabled as NT default
M
M Tue Jul 30 10:21:44 2002
M calling db_connect ...
M db_connect o.k.
M
M Tue Jul 30 10:22:25 2002
M rdisp/reinitialize_code_page -> 0
M
M Tue Jul 30 10:22:53 2002
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020730.AUD
M
M Wed Jul 31 00:00:52 2002
M SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020730.AUD
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020731.AUD
M
M Thu Aug 01 00:00:49 2002
M SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020731.AUD
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020801.AUD
M
M Fri Aug 02 00:00:51 2002
M SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020801.AUD
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020802.AUD
M
M Fri Aug 02 00:14:09 2002
M *** ERROR => ThCallHooks: event handler rsts_before_commit for event BEFORE_COMMIT failed [thxxtool3.c 235]
M ***LOG R38=> ThICommit3, db_commit98 ( 001024) [thxxhead.c   10641]
M ***LOG R18=> ThPrivCommit, ThICommit () [thxxhead.c   11307]
M in_ThErrHandle: 1
M *** ERROR => ThPrivCommit: ThICommit (step 4, th_errno 9, action 2, level 1) [thxxhead.c   8277]
M
M Info for wp 13
M
M    stat = 4
M    reqtype = 4
M    act_reqtype = 4
M    tid = 13
M    mode = 0
M    len = 24
M    rq_id = 6643
M    rq_source = 1
M    last_tid = 13
M    last_mode = 0
M    rfc_req = 0
M    report = >                                        <
M    action = 16
M    tab_name = >                              <
M
M Modeinfo for User T13/M0
M
M    tm state = 2
M    uid = 14
M    term type = 0x0
M    display = 0x0
M    cpic_no = 0
M    cpic_idx = -1
M    usr = >SAPUSER     <
M    terminal = >                    <
M    client = >800<
M    conversation_ID = >        <
M    appc_tm_conv_idx = -1
M    imode = 3
M    mode state = 0x42
M    th_errno = 9
M    async_receives = 0
M    cpic_receive = 0
M    em handle = 3
M    roll state = 4
M    abap state = 4
M    em state = 3
M    eg state = 1
M    spa state = 3
M    enq state = 0
M    next hook = T-1/U-1/M255
M    master hook = T-1/U-1/M255
M    slave hook = T-1/U-1/M255
M    debug_tid = -1
M    mode type = 0x1
M    debug = 0
M    lock = 0
M
M
M Sat Aug 03 00:00:55 2002
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020803.AUD
M
M Sun Aug 04 00:00:49 2002
M SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020803.AUD
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020804.AUD
M
M Mon Aug 05 00:00:49 2002
M SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020804.AUD
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020805.AUD
M
M Tue Aug 06 00:00:49 2002
M SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020805.AUD
M SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020806.AUD

Thank you, Bhaskar,
I have performed consistency check for temse objects and all the comments are displayed in red color.
Does it mean that objects are inconsistent. But, no comments states that object are inconsistent.
I have attached the comments displayed,
Consistency check of table TST01 / TemSe objects
This comment occurs repeatedly, Unable to access the related file           Length = 0
Incorrect number of data lines in TST03
Object with part number 1 missing
Object reset                     Length = 0
The related file has an incorrect length
Consistency check of table TST03 / TemSe data
No object found in TST01
May i delete all objects, as all the comments are red in color.
Dayanandan.A

How to find out number of background work processe available in the system?

Hi All,
I have a FM that triggers a background job using JOB_OPEN, ABAP_SUBMIT and JOB_CLOSE. But the problem is if there are no background work processes available at that moment, it does not return error. Not sure whether the job is even scheduled!
Is there a way to find out if there are any background work processes available in the system? I know a FM SPBT_INITIALIZE which gives info about dialog work processes. Is there any other FM similar to this which gives info about background wp??
Regards,
Shailesh

your Job will remain in a queue by message handler. once workprocess is free, your job gets scheduled
by the way, you can use the functionality used in FM TH_DISPLAY_WORKPROCESS_LIST to read the workprocesses
the command which gets you the workprocess is:
CALL 'ThWpInfo' ID 'OPCODE' FIELD OPCODE_WP_LIST
ID 'TAB' FIELD LIST_STATE_WPLST-TABL
ID 'CPU' FIELD LIST_STATE_WPLST-CPU.
check how its written in include LSDEBF01, form SET_LIST_WPLST
Edited by: Soumyaprakash Mishra on Dec 12, 2011 12:17 PM

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.

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

Send mail to a specific user group when an Inbound Idoc processing fails

I am using standard Message type DEBMAS, but the process code is customed (say ZDEBM as the function module is customed). Can you tell me what configurations are required to activate the error notification message to a user when the inbound idoc fails?

hi,
i think u need to check tcode swu3 for automatic workflow customizing and check in we40 (error AND STATUS PROCESSING) whether the processing code is assigned to the workflow task.
if it is assigned,the workflow will be automatically triggered and the mail will be sent to the user by itself.
ALE error handling uses workflow. A standard task is provided for each message type. Task TS20000051 is used for all BAPIs.
Workflow functions as follows:
A task (work item) is generated for the error handling and stored as a message in the inboxes of the employees responsible.
If one of these employees processes the work item, the standard task method for error handling is started. The user can, for example, restart IDoc processing.
If the IDoc is processed successfully, the work item is deleted from the inboxes of all the employees involved.
For this procedure to function, the employees responsible for a particular message type and partner (sender or receiver) must be defined as follows:
1. A hierarchy of organizational units (for example, "sales office") and positions (for example, "customer officer for customer X") is created and employees are assigned to it.
2. The standard tasks for error handling (for example, an error related to an inbound sales order) are assigned to the relevant organizational units or positions (for example, "sales office").
3. The organizational unit, position or employee responsible for dealing with the error are specified for each partner and message type in the partner profiles.
If an error occurs, the system determines:
1. The employees responsible using the staffing schedule of the organizational unit or position linked to the standard task.
2. The employees defined in the partner profiles (using position, user ID, or organizational unit).
3. The employees appearing in both groups represent those who will receive a work item in their inboxes.
regards,
pankaj singh

Background Idoc processing

Similar Messages

Maybe you are looking for