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.

Similar Messages

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

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

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

Partner profile agent

Hello
Someone has changed the agent name in the partner profile(LS)
Can i track who made these changes?
Thanks and Regards
Manu

Hi,
The LS details would be updated in table EDPP1. To check for the logs or history, go to transaction SCU3 (evaluation of change logs) and check the logs for these tables by providing this table name, date duration and select the "Tables" radio button under the criteria "Evaluation for". You would be able to view the user who created or changed or deleted the partner profile along with the message type and the date of change made.
This could be possible only if the table logs is activated.
~Bineah.

Partner Profile and its configuration.

Hi all,
I am creating an SD IDoc using EDI and send it between two servers.
I need to know what is a partner profile and why should we create it.
what are the steps to be followed in maintaining a partner profile and its configuration.
Any pointers will be highly apppreciated.
Thanks in advance,
Regards,
Jose
Edited by: Jose Anthony Reddy on Dec 17, 2007 11:23 PM

Hi Jose,
Below is a material you can go through .
Creating an Outbound Partner Profile
Here you must enter the data manually. Alternatively, you can also transfer the default values from Customizing.
If you are not yet on the change screen of your desired partner, choose SAP Menu ® Tools ® IDoc Interface/ALE ® Administration ® Runtime Settings ® Partner Agreement (WE20).
1. Position the mouse on your partner in the required partner type node. Choose in the Outbound Parameter table.
Key Fields
2. You have already determined partner number and partner type in general partner processing. The partner function from the master data defines the addressee, that is, it is used for further classification purposes. If you have selected outbound processing under Message Control (MC), the function must be identical to the corresponding Message Control field. Otherwise, it is optional.
Partner A (customer 1110) wants to order a material from partner B (vendor 1014). Partner B is of the partner type LI (vendor) and must choose the Message Control value VD (vendor) as the partner function because orders must always be processed using Message Control.
3. Specify the business process with the logical message, within which the IDoc type is used. The logical message is described by three parameters: The message type is based on EDIFACT message types: For example, a purchase order is of type ORDERS. You can further divide the message type with the optional fields message code and message function.
4. Configure the test indicator if you want to send the message as a test.
Message, partner and test indicator are the seven key fields of the outbound partner profiles (the client comes in addition to these). Also see the graphic at the end of this section.
Other Fields
5. In the Outbound options tab page, you can determine whether IDocs are forwarded immediately to the receiving system. You should ensure that your entries are compatible with the Message Control priorities, if you have chosen outbound processing under Message Control. A list of recommended combinations is provided in the section Outbound Processing Under MC: Procedure.
6. You have already defined the Recipient port in Port definition.
7. If a port of type TRFC is used, the Queue Processing field is visible. You can use the indicator to specify whether IDocs are to be sent with qRFC. This sending technique is only possible for recipient SAP systems as of SAP Web AS 6.20.
You should only set this flag if it is really necessary that the IDocs sent are received in the receiving system in the same sequence as they were sent by the sender system. Queuing can cause posting delays in the receiving system, because an IDoc in the queue cannot be posted. In this case, the following IDocs in the queue cannot be posted until the error is resolved.
8. If you have set the Queue Processing indicator, the Rule Name field, which you must then also maintain, appears as well. The rule name defines the rules for queue names. You can specify these rules in the transaction qRFC IDoc Queue Name Rules (WE85).
9. Specify the IDoc type as the Basic type with or without extension. If you want to use a view of your IDoc type (for example, to improve the performance), specify this here.
The figure below shows the m-to-n relationship between logical messages (business meaning) and IDoc types (technical format). Message 1, for example, is always assigned to one IDoc type, while message 3 is assigned to two IDoc types. IDoc type 2, in turn, is also assigned to 2 logical messages.
10. The segment release specifies the release from which the segment definitions (not the IDoc type definition) originates. We recommend that you leave this field blank so that the most recent segment definition is used.
11. You can propose an EDI standard, version and EDI message type for the receiving system in the tab page EDI Standard. Most subsystems, however, should be able to determine these EDI settings themselves (from the logical message).
12. You can define permitted agents for cases in which exceptions occur. This entry overrides the entry in the general partner profiles. Depending on the message, therefore, the exception can be handled by different agents of the same partner.
13. You can specify whether syntax errors are to be ignored or are to lead to a processing error (Cancel Processing flag under syntax check in the tab page outbound options). For more information about exception handling and permitted agents, refer to the following section: Exception Handling
14. If your hardware supports it, create partner and message specific telephony data for outbound IDocs. For more information, see General Partner Profile.
Graphic: Outbound partner profile fields (general)
Key fields are shown in gray. The values for partner, message and test indicator (and client) therefore provide a unique ID for the IDoc type in outbound processing.
Regards,
Praveen

Partner Profile Configuration(Outbound Enteries)

Hi,
I was trying to make a business partner with the BP Role Master Tenant with Customer Account. At the time of saving I got following error:
Entry in Outbound Table not found
Message No E0400
No partner profile(Outbound) could be foundusing following key
B3TCLNT800/LS//HRMD_ABA///
This refers to key fields in Table EDP13
RCVPRN Partner Number
RCVPRT Partner Type
RCVPFC Partner Function
MESTYP Logical Message
MESTYP Message Code
MESCOD Message function
TEST Test indicator
Please check EDI profiles.
And it directed me to transaction code WE20.
Could you please help me in making the desired settings and explain why this needs to be done.
Regards,
Lata

Hi,
I guess either you are using CRM or Flexible Real Estate Management.
Pl confirm the exact transaction code you are using. Are you using BAPI ?
For creating the Partner profile,
Go to WE20,
Click on Create button.
Give the Partner Number, Give Partner Type as " LS"
User type- US
Agent - Your User ID
Give the Message types in the Outbound/ inbound parameters.
Pl reply for further clarifications
Thanks
Siva

EDI Partner Profile creation at Transaction Code FI12

How is the partner profile created when you select the Icon Partner Profiles, which is transaction code WE20 that is accessing from transaction code FI12.
The type is B for bank. Can the partner number be a end user defined number? Can this be the vendor number for the bank? That does not appear to be an option!
Here are my questions of the Post processing permit agent design.
How are the values for the "Types" created?
Thanks
Chris Courter

Rohan Patil wrote:>
> BEGIN = 1.
> edi_dc40 segment values
> SEGMENT = 1.
> TABNAM = EDI_DC40.
> MANDT = 120.
> DIRECT = 2.
> IDOCTYP = CREMAS05.
> MESTYP = CREMAS.
> SNDPORT = SAPNBD.(XI port)
> SNDPRT = LS.
> SNDPRFC = LS
> SNDPRN = NXICLNT120.
> RCVPOR = SAPNED.(ECCport)
> RCVPRT = LS
> RCVPFC = LS
> RCVPRN = ECCCLNT120(ECC partner number).
Hello Rohan,
IDocs SNDPRN/SNDPRT/MESTYP will be taken in SAP for processing the received IDOC,so in your case either you need to create the partner profile NXICLNT120 with all inbound details or need to change the same in mapping and pass the values of your partner in SNDPRN SNDPRT fileds of control record
HTH
Rajesh

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

Task properties - General task - Partner profile

Hi Experts,
I'm using user decision step for manager approval, and in development server i've selected task as general task in task properties and everything was working fine in development server.
When above workflow development transported to testing server, the task properties are not transported. So, agent assignment is de-activated. And when i'm trying to set general task attribute in task properties, its saying "Entry in outbound table not found" error message. Can anyone help me in resolving this.
Entry in outbound table not found
Message no. E0400
Diagnosis
No partner profile (outbound parameter) could be found using the following key:
DC1CLNT10/LS//HRMD_ABA///
This refers to the key fields in table EDP13:
RCVPRN Partner number
RCVPRT Partner type
RCVPFC Partner function
MESTYP Logical message
MESTYP Message code
MESCOD Message function
TEST Test indicator
Thanks in advance,
Siva Sankar.

Hi Siva,
I have always found that I need to go make change the agent assignment on custom tasks to 'General' as the workflows get transported - or you can investigate here:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d00a1cb4-913c-2c10-d991-caf663ab9b16&overridelayout=true
As Jocelyn Dart has said:
Folks, This is an oldie but a goodie.
You need to execute program RHMOVE30 to add your General Task settings to Transports.
Enter your task numbers (you can enter a workflow and use eval path TASK_HIER to pick up all sub tasks) Select the Transport checkbox
On the second screen
Select all and press Add to Transport
Select all again and press Transport/Delete
You should get a message confirming they have been added to your change request.
You will see infotype 1217 entries on your transport request.
However your issue seems to be a different one. I searched and it looks as though you need to check partner profiles using WE20? Have you tried this?
Hope this helps,
Sue

Regarding partner profile

HI all
i am configuring an outbound partner profile for an outbound IDOC ,when i try to give the <i>post processing:permitted agent</i>,here i am getting this message <i>NO ACTIVE PLAN VERSION EXISTS</i>.
CAN ANYBODY HELP ME ON THIS
regards
kish

Hi,
Go trough this
2 Introduction
Configuring IDoc adapter in Exchange Infrastructure 3.0 requires some configuration on the SAP
systems, for both XI and the backend system where the IDoc message is to be sent. These steps, although
simple, are many times missed or mis-configured, causing the delivery of messages to fail.
Since IDoc adapter uses the ABAP stack, instead of J2EE, the configuration requirements are mainly in
ABAP.
Setting up IDoc adapters requires the XI integration server to be able to communicate with the backend
SAP system, and also to make sure that the Logical System Name used when posting IDoc exists on the
backend SAP system.
3 The Step By Step Solution
The basic steps for the IDoc configuration are outline below:
1. Configure SM59 on XI to communicate to SAP backend system.
2. Configure port on XI for IDoc communication.
3. Create or verify the Logical System Name on the SAP backend system.
4. Create or verify business system in XIs System Landscape Directory.
5. Verify the Logical System Name of the business system.
6. Verify or add the Logical System Name for the sender business system.
7. Create/configure the Communication Channel for the IDoc receiver adapter
3.1 Configure SM59 on XI to communicate to SAP backend system.
1. Using transaction SM59, create an RFC destination with Connection Type = 3.
In this example, the RFC destination name is NDVCLNT510.
2. Enter the logon information:
3. Test the connection by clicking on Testing connection and Remote logon.
Both must be successful.
3.2 Configure port on XI for IDoc communication.
4. Go to transaction IDX1 on XI, and create a port. In this example, the Port name is SAPNDV.
     The Port name must be in the form of SAPxxx, where xxx is the system ID of the backend SAP
system.
     The Client must be the client number of the backend SAP system.
     Select the RFC Destination which was created in the previous step.
3.3 Create or verify the Logical System Name on the SAP backend system.
5. Enter transaction SALE on the SAP backend system.
6. Create or verify the Logical System Name. In our example, NDVCLNT510 is verified.
3.4 Create or verify business system in XIs System Landscape Directory.
The business system name for the SAP backend system must contain a valid Logical System Name. This Logical System Name is the one verified or created in the previous step.
7. In the System Landscape Directory, select the SAP backend business system. If one does not exist, then create the business system. Verify the Logical System Name.
3.5 Verify the Logical System Name of the business system.
8. In the Integration Directory, doubleclick on the business system (in our example, it is NDVCLNT510).
Navigate the menu:
Service Adapter Specific Identifiers.
If information is empty or incorrect, then it will have to be synchronized with the content of the System Landscape Directory. Follow the steps below for synchronization.
9. (Optional) Synchronization of the business system in Integration Directory to the business system in System
Landscape Directory.
     Double-click on the business system in the Integration Directory.
     Switch to Edit mode.
     Select menu: Service Adapter-Specific Identifiers
10. (Optional) Within the dialog box, click on the button as indicated below to resynchronize.
11. (Optional) If the expected data from the System Landscape Directory is not updated, then the SLD cache may need to be cleared first.
3.7 Create/configure the Communication Channel for the IDoc receiver adapter.
15. In the Integration Directory, create an IDoc receiver communication channel.
     The RFC Destination is from step 3.1.
     The Port is from step 3.2.
NOTE:
There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.
4 Appendix
Transaction: IDX2
There are a couple of situation where IDX2 can be useful on the XI system.
1. When we want to test connection between the XI and SAP backend system.
2. When an IDoc has changed, and the meta data stored in XI needs to be update. When an IDoc is sent from the SAP backend system to XI, XI will first check to see if the meta data for the IDoc is already in its persistent cache. If not, then XI will use the configuration in IDX1 to retrieve the IDoc meta data from the backend system. If the
meta is already in cache, then it will NOT do so. Therefore, when an IDoc has changed, it is necessary to manually update the new meta data on XI, or delete it from the cache, so that the latest version can be retrieved. IDX2 is used for this purpose.
Go to transaction IDX2 and click on Create.
Enter the IDoc Type and the Source Port as defined in step #2. Click Continue.If successful, the following will show up. If error occurs, then the IDX1 configurations will need to be re-checked.
Regards
Hemant
award points if find helpful

Partner Profiles for EDI message output settings

HI,
Iam creating Partner profiles settings for Message output through EDI.
While entering data for partner type Li Vendor.
Iam selecting User Type Organizastional Unit.
& while selecting Agent no information found.
Iam getting error as Object type O, ID 50010120 unknown (please observe upper/lower case)
How can i create Id for objects types. ( how can i create Agents)
pls help
Regards
Sunil

What are you trying to do?
Agents in WE20 are used for post processing of failed IDoc's.
You can use:
Work center
Job
Organizational unit
Person
Position
User
If you require agents, which type do you want - organisational unit?
If you do not require post processing options - use User with your ID.

Partner profiles and ports

How to transport the configuration of partner profiles and ports from Development to Quality systems.

Hi vidya,
Go through this hope u can get the solution.
WE20 Partner Profile
Here we create partner profile for each and every partner from / to which
the messages will be exchanged.There are 6 types of PF generally only
profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
We specify the partner number and partner type and the agent and
the agent type responsible for handling of errors .
For every message send to the partner we have a outbound record and for
evry message coming from the partner we have the inbound record .
We specify the message in the otbound/inbound records ,double
clicking will take us to the detailed screen where the IDOC Type ,Port
and whether the IDCO will be immediatelt processed or collected are
mentioned.
WE21 Port Definition.
There are 6 types of ports but only 2 types File and Transactional RFC
types of ports are important.
We have to specify the RFC Destination before a port can be created.
SM59 RFC Destination
Here we specify the login settings for the destination including
the I.P address or Application Server name and the User name and
password.The information entered here is used to run Remote Function
Calls(RFC ) on the destination server .We can create number of types
of RFC Destinations but 3 types are important .
R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
The name of the RFC destination should be same as that of Logical
System as it helps in creation of automatic partner profiles.
BD64 Distribution Model . Also known as Customer Distribution Model Used to
define all the messages that will be exchanged between remote systems
and the name of thes logical systems. Any filters can also be specified.
The model once created has to be distributed on every system which will
be communicating ,It can be maintained on only One system.
Reward points if helpful.
Thanks
Naveen khan

Regarding ports and partner profiles in ALE.

Hi All,
Please tell me how to transport the partner profiles and ports from Development to Quality systems.
Please reply asap.

SALE Area Menu for ALE configurations.It includes transactions for
Logical System definition and linking it to a client, Transactions for
RFC Destination and Port Definition Etc.
SM59 RFC Destination
Here we specify the login settings for the destination including
the I.P address or Application Server name and the User name and
password.The information entered here is used to run Remote Function
Calls(RFC ) on the destination server .We can create number of types
of RFC Destinations but 3 types are important .
R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
The name of the RFC destination should be same as that of Logical
System as it helps in creation of automatic partner profiles.
WE21 Port Definition.
There are 6 types of ports but only 2 types File and Transactional RFC
types of ports are important.
We have to specify the RFC Destination before a port can be created.
WE20 Partner Profile
Here we create partner profile for each and every partner from / to which
the messages will be exchanged.There are 6 types of PF generally only
profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
We specify the partner number and partner type and the agent and
the agent type responsible for handling of errors .
For every message send to the partner we have a outbound record and for
evry message coming from the partner we have the inbound record .
We specify the message in the otbound/inbound records ,double
clicking will take us to the detailed screen where the IDOC Type ,Port
and whether the IDCO will be immediatelt processed or collected are
mentioned.
Reward points if helpful.
Thanks
Naveen khan
Message was edited by:
Pattan Naveen

Send emails to specified users,but SAP is picking from partner profile WE20

Hello
By using FM 'SAP_WAPI_START_WORKFLOW', passing with task = 'TS00007989' amd triggering workflow, if at all my IDOC get fails! This work flow/task will send en emaill to the Permitted Agent defined in partner profile, WE20 for that partner type/message type, fine. In our case, the Permitted Agent is 'Workflow Administrator', so he is getting emails for IDOC errors.
But, we do not want to let SAP pick this Adminstartor from partner profile, we want to maintain a custom table for users IDs and we want to SAP pick this receivers/recepients from this custom table for User IDs
Note: already am passing user IDs in ' agents' table parameter explicitly, but still SAP is picking workflow admin from partner profile!
How can i achive this? any user-exit or any BADI or ENH? Pls. let me know
Thank you

HI
Can you please give inputs on following
1. Where you are triggering WF using 'SAP_WAPI_START_WORKFLOW'
2. is that workflow custom workflow ?
There in one way triggering custom workflow when IDoc is in error mode.
1. When you assign function module to process code there is ALE table button in front of FM.
2. Once you click that you can assign Object type, start event, end event.
3. To this particular event custom worklfow will be triggered.
4. In your custom workflow you can select agents as per your requirement.
Regards
Sachin

Agent in Partner profiles

Similar Messages

Maybe you are looking for