Post processing agent in partner profile

Hi
Inbound idoc fails. The partner profile has a user (US) in the post processing:permitted agent, both on the actual partner (LS) and on the inbound message type. I would expect to see the error in the inbox of the business workplace, but I see nothing! - what have I done wrong?
Cheers
Rob

Hi,
I think for this you have to configure the workflow notifications for inbound process.
Check if they are in place.
Check this link.
http://sap-f3.blogspot.com/2009/11/workflow-configuration-of-inbound-idoc.html
Hope it helps.
Regards,
Raj

Similar Messages

Agent in Partner profiles

Hi Guru's.
Can any tel me the impotance of AGENT in partner profile?
Regards,
Krishna
Edited by: Shiva Krishna on Jun 26, 2009 8:28 AM

It can be used by Workflow to trigger events, for example notification to users if an iDoc has failed.
Cheers, Paul.

Anyway to automatically change processing mode on partner profile???

We have a situation where we need to lock down SAP for a few hours every night so a credit reorg job can run. However, at the same time we need delivery idoc's to be sent into the same SAP system but we cannot allow them to post since they may interfere with credit job. For business reasons this job MUST run and everyone must be locked out of SAP while it runs. We dont have the option of collecting outside of SAP unfortunately.
During normal operation we have the partner profile entry for deliveries to process by triggering immediately since the delivery IDOC is essential for normal business operation. While this job runs(say 10pm - Midnite) we'd like to change it to trigger by background program so the IDOC's are in SAP ready to be processed as soon as the job is complete.
TO summarize, this is how we'd like to set it up:
1) Lock out all SAP users except one used to send in Delivery IDOC's
2) Change inbound parameter for deliveries to trigger by background job
3) Continue sending deliveries into SAP while job runs for 2 hours
4) As soon as job finishes, run RBDAPP01 to process collected delivery IDOC's
5) Reset inbound parameter for deliveries to trigger immediately so any new delivery IDOC's get posted since SAP is now up and available.
Is there anyway to do this via ABAP or some type of event handling???
Thanks!!!

Once u set up the ALE configuration,
if u want the idocs for the message type to be sent automatically whenever changes are made u need to do the following:
1. BD61 -> CHECK ACTIVATE CHANGE POINTERS GLOBALLY
2. run the program RBDMIDOC , GIVE THE MESSAGE TYPE
AND SCHEDULE THE PROGRAM IN BACKGROUND SO THAT CHANGES ARE
UPDATED AT THE SCHEDULED TIMES.
Hope this helps u

Error while posting Inbound Idocs-"EDI: Partner profile not available"

Hi,
I am getting the error "EDI: Partner profile not available" Status -56 while creating inboud Idocs.
I have done the following steps so far
1.Created IDOC basic Type and Message Type. (Custom)
2. Created process code to process the IDOC.
3. Use the FM IDOC_INBOUND_WRITE_TO_DB to create the inbound IDOC.
4. Use the FM IDOC_START_INBOUND to process the IDOC.
Is ther anything else that i have to do inorder to post the idoc sucessfully.
Thanks in advance
-Nishant
Edited by: nishant patel on Nov 13, 2009 10:35 AM
Edited by: nishant patel on Nov 13, 2009 10:41 AM

Hi,
Check in WE20 if the partner profile is configured for the idoc type and the message type. That might be the cause of the error.
Also make sure the same partner profile details are sent to the control record. Partner profile details are stored in the table EDP13.
Hope this helps
Regards
Shiva

Work Agents in Partner Profile

Hi Guru's
I need to set up a Workflow for gathering the Inbound IDOC which are in error state. I did the following tasks.
1. Setting up the Work agent and assigned the users ( who receives the WF messages), thro PPOME
2. Assign the work agent to the respective partner profiles.
However I am not able to receive any messages in my Inbox, Did I miss any step here? Please let me know.
thanks in advance
Ganesh

HI,
There are different scienarious for this problem .
1. Check the Assigned agents are correct?
2. Check the workflow Event is triggerd are not.
~linganna

Cdm and partner profiles

can help me out in,,,,,What are CDM and Partner Profiles in ALE??

Hi Praveen,
Chk these links
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
ALE
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.

***Reward Points if Useful
Regards
Gokul

Generating partner profile for File to Idoc(CREMAS) scenario.

Dear friend,
Completed all the steps in SLD, IR and ID.
I do not know how to create Partner profile and I skipped this step.
While testing I got the error "Unable to convert sender service to an ALE logical system".
I think i got this error because I have not created partner profile.
Could anybody tell step by step process of creating partner profile including logical system names( Sender and Receiver)?
I have seen many blogs and i couldn't get clear picture on how to generate partner profile.
My sender system is XI server and receiver is R/3.
I have created RFC destination, Port also.
Thanks in Advance
Chiru

generally u create partner profiles using transaction WE20.
SAP Menu -> Tools -> IDoc Interface/ALE -> Administration -> Runtime Settings -> Partner Agreement (WE20).
go through this link for step by steps
http://help.sap.com/saphelp_nw2004s/helpdata/en/dc/6b808e43d711d1893e0000e8323c4f/content.htm
http://www.thespot4sap.com/Articles/SAP_ALE_Configuring.asp

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

Workflow not routing to agent specified in partner profile

have included below notes regarding the mis-routing of workflow messages of "translation error" STATUS message idocs that are uploaded into R/3.
The testing that I have been performing has been in Development System. The first thing that I check is that the Partner profile parameters are set to send the STATUS message type idoc to an agent via t-code we20. This agent does exist in the organization structure found at t-code ppome. I have been using the logical system (partner type LS) user=GEIS, inbound parameter message type=STATUS, message variant=AP, where myself is setup as the agent to receive workflow.
When processing an inbound STATUS idoc containing an error code of "05", meaning that translation failed on the outbound corresponding idoc (e.g. invoice, desadv, etc.) in the EC subsystem, workflow should be triggered and route the message to the agent specified at the message type level of the partner profile. In the event that an agent is not configured at the message type level of the partner profile, then the workflow message should be routed to the agent specified at the partner profile global level. However, in the event that an agent is not specified at the message type level or partner profile global level, then the workflow message should be routed to the IDOC Administrator, which is configured in t-code we46.
The results of my testing has been that regardless of the agent configuration set at the message type level or partner profile global level, all workflow messages are routed to the IDOC Administrator configured in we46.
The request is to have development work completed so that error STATUS idocs can trigger workflow messages that will be routed to various agents for resolution, versus workflow messages being routed just to the IDOC Administrator - which is how it is working today.
I would greatly appreciate for your immediate response.
Regards,
Shankar

Hi Stacey
If DEV is working and PRD is not have you gone through and compared both and ensure latest MSMP configuration in PRD has been activated?
Also, is the approver COCHGG00 also the Role Owner?
Are you able to show you MSMP configuration? It's makes sense to analyse the log in the context of your configuration. E.g. does the Z_ADDTNL_ACCESS_PATH path have two stages: Manager and Role Owner of which there is a routing rule on the Manager approval to go to the NO_ROLE_OWNER path where the business role has no role owner?
Regards
Colleen

Could any body tell me the significance of Partner Profiles in IDOC PROCESS

Hi,
Could any body tell me the significance of Partner Profiles in IDOC process.
Thanks in Advance,
BSV.

Hi,
The partner profile is used to validate the sender and receiver system for a given message type and to assign to the correspondence process code (function module) to post the IDoc to application system.
This applies for both Inbound and Outbound IDOC's.
Also please check this link for more information.
http://help.sap.com/saphelp_46c/helpdata/en/dc/6b803343d711d1893e0000e8323c4f/frameset.htm
Regards,
Ferry Lianto

Posting IDocs, partner profile setting

Hello,
I want to ask for advice.
It happens IDoc hangs on R/3 side while requesting data to load them to BW. This IDoc has no error and after manual processing (BD87) data are transfered correctly and IDoc posted. It is message type : RSRQST and it has set up " Trigger by background program" option in Partner profile / inbound parameters.
What could be the reason that IDocs hang without any error?
Addtionally:
what is recommended as IDoc processing option?
is it : Trigger by background program or trigger immediatelly?
Thank you in advance, Peter

Thank you for fast feedback.
I checked notes 561880 , 555229 and 535172 but they point to issues with resources during IDoc processing to application. I am not quite sure if this is my case. I Think my problem occured before the IDoc processing to appliccation.
I suppose if there is a problem with resources the IDoc gets " status 64, "NO RESOURCES, IMMED. PROCESSING NOT POSSIBLE:
However the problem I am referring to is that IDoc gets "Status 64, No filters , No conversion , No version change . If I understand it right this means that IDoc was processed by ALE and waits for further processing to Application. Unfortunately it doesn't start.
any idea what could be the problem? or does it really have something to do with resources?
Thank you,
Peter

Define Port, Partner Profiles, Process Code

Hi All,
Please provide the following valueble information
Define the below and why do we create them?
1. Port
2. Partner Profile
3. IDOC type and IDOC
4. Process Code
5. Message Type
Thanks and Regards
Sowjanya

>>1. Port
Ports are channel through which idocs are exchanged.
>>2. Partner Profile
Partner Profile specifies the kind of message that we are going to exchange with our business partner
>>3. IDOC type and IDOC
IDoc type defines the structure of the idoc. IDoc is a container which carries the data from one system to the another.
>>4. Process Code
Process Code refers to inbound function module which will read the data from the idoc and post it in the system.
>>5. Message Type
Message Type defines the kind of data that you are exchanging with your business partner.
Cheers,
Hakim

Partner profile is not workin for automatic vendor posting

Dear SAP Gurus,
When i am doin the intercompany billing so the RD04 output calls but the status is red and when i see the processing log the system says that EDI: Partner profile not available..and also vendor A/P dont generate..even though i have make all the setting and still its not working...i really dont know that wht i am missing....can any one tell me the setting for the partner profile? that wht setting i have to do for the customer outbound or inbound processing and wht settings for the vendor outbound or inbound processing? i will appreciate for your fast response...
Mohsin

Hi Shree,
Why we are goin to make for vendor or bank? this is purly the cross company sales scenario.....the thing there is 2 compnay code in one client.....customer comes to company A and ask for the material and company A dont have material.....so company A makes sales order and in the sales order define the plant for the company B......customer goes to compnay B and take the goods....so delivery will from company B....2 invoices will be generated one for the customer from company A and 2nd invoice is generated from compnay B to company A......so now A/P is not genrating from Company A? even though every thing is maintain.....but still is not working......and its saying that partner profile is not avaliable....even though its maintain for the internal customer and the internal vendor.....so please can u help me on that.....
Regards,
Mohsin

Process code & Partner Profile Issue

Hi Experts ,
Hi ,
I need to configure partner profile with a external system . I will be receiving customer data from the ext System .
I though of using msg type DEBMAS and msg type
and process code DEBM. I see its uses function module IDOC_INPUT_DEBITOR.
So what exactly this function module does ?
I was wandering if I need to create new Process code / Function Module .
My requirement is receiving the customer data along with address , shipping informations , customer no . So that when I drop orders its becomes available.
Thanks
MM_sD

Hi ,
Check all the settings needed for an R/3 - XI- R/3 scenario..... In ur case R/3 to XI is working fine and u have to check the XI-R/3 side.
Check the RFC destination ( Both in XI and in R/3)
Check the logical system name
PORT, Partner profile .....
Regards,
Jude

WE20 - post processing: permitted agent tab

Hi ,
I need to create a inbound TXTRAW message type for a comapny code which I have done. Then in the screen where you give the process code , the next tab is post processing: permitted agent tab ... here my requirement is that this mail should go to a group of people ... How do I achieve that ?
Please help.
Thank You,
SB.

Hi MxG,
I have created a Org unit "US90" ... but how do I directly assign users to that Org ? ... After creating Org ... it is only allowing to create positions .... and if I create position's (AP_US90_TXTR) and assign the users to the position ... In WE20 if I write "AP_US90_TXTR" in the agent field then it gives an error "Object type S, ID AP_US90_TXTR unknown (please observe upper/lower case)" ... So I am unable to proceed. Could you please help me?
Thank You,
SB.

Post processing agent in partner profile

Similar Messages

Maybe you are looking for