Disabling user through API call -process task-followed by an Enable User...

Hi,
I am running on OIM 9.1 BP11. I implemented a process task to disable the user based on a URS form field change.
I can confirm from the log file and the resource that the Disable user (xellerate user) happened. But the user got enabled back right away. The log file showed that a scheduled task named "Enable User After Start Date" ran and enable the user. So, I disabled that scheduled task.
Then I repeated the test again. I observed the same behavior of user being disabled and enabled again but this time, OIM called an adapter. This is what I observed in the log file:
20988 INFO,20 Oct 2010 12:21:56,519,[XELLERATE.DATABASE],DB read: select evt.ev t_key, evt.evt_name, evt.evt_package, mil.mil_name from mil mil, evt evt w here evt.evt_key = mil.evt_key and mil.mil_key=10
20989 DEBUG,20 Oct 2010 12:21:56,519,[XELLERATE.DATABASE],select evt.evt_key, ev t.evt_name, evt.evt_package, mil.mil_name from mil mil, evt evt where evt. evt_key = mil.evt_key and mil.mil_key=10
20990 INFO,20 Oct 2010 12:21:56,519,[XELLERATE.PERFORMANCE],Query: DB: 0, LOAD: 0, TOTAL: 0
20991 DEBUG,20 Oct 2010 12:21:56,519,[XELLERATE.SERVER],Class/Method: tcBusiness Obj/getSqlOperationFromMembers entered.
20992 DEBUG,20 Oct 2010 12:21:56,519,[XELLERATE.SERVER],Class/Method: tcBusiness Obj/getSqlOperationFromMembers left.
20993 DEBUG,20 Oct 2010 12:21:56,519,[XELLERATE.ADAPTERS],Class/Method: tcADPCla ssLoader/getClassLoader entered.
20994 DEBUG,20 Oct 2010 12:21:56,519,[XELLERATE.ADAPTERS],Class/Method: tcADPCla ssLoader/getClassLoader left.
20995 DEBUG,20 Oct 2010 12:21:56,520,[XELLERATE.ADAPTERS],Class/Method: tcADPCla ssLoader/findClass entered.
20996 INFO,20 Oct 2010 12:21:56,530,[XELLERATE.ADAPTERS],Adapter: Enabling the User was initiated for the task: Enable User.
20997 INFO,20 Oct 2010 12:21:56,531,[XELLERATE.JAVACLIENT],System Event Handler : Enabling the User
I did exactly the same disabling user process at another client and it worked fine. I don't understand what causes OIM to call this system Event handler to re-enable the user.
Please help.
Thanks
Khanh

Do you have any Entity Adapter or Event Handler or Trigger which enables user for some condition ?
Check your environment. If you have please remove that and try.
Does this user has and provisioned resource ? If yes, try for some other user which doesn't have resource provisioned.

Similar Messages

Add approval task through API call

Hello, I am attempting to solve the following problem.
I have a UDF defined on the Resource Objects form (OBJ table), this filed contains a comma delimited list of OIM groups which is of size n (based on the resource object).
I would like to create an approval task for each group in this list. In addition i would like the name of each task to show up as the group name. so when a user logs into the UI and looks at the approval details the see the approval task as the group name.
I have been able to add a task using tcProvisioningOperationsIntf.addProcessTaskInstance API however this API does not allow me to modify 1) the group to assign the request to and 2) the name of the task.
thanks

Hey Kevin, thanks for responding.
This query will allow me to get the process task key, so i can be added to the approval task via. tcProvisioningOperationsIntf.addProcessTaskInstance. However the issue is, no task currently exists. So before i can add an instance of the task i have to actually create a new task. but i was un-sure how to accomplish this through api calls.
The goal here is to allow a list of groups to be configurable at the resource level without having to modify the approval process.
thanks

How to call Process Task in AD User proccess definition from Xellerate user

Hello,
I need a help from you guys.
I have one customized process task in "Xellerate User" Process definition. When my this task executes completely, I would like to call one of the customized process task in "AD User" process definition from xellearte user. Is there any way we can do that?
Thanks for your any help....

There are lots of ways to accomplish this. I haven't read through the other posts, but here are a few options.
Option 1 - Create a second task that also triggers at the same time, but set the task you already have as preceding. Then on your second task, write whatever code is needed to update a field, insert a new task, whatever the function is that's needed.
Option 2 - On the completion response of your original task, just use the response code to trigger the second task from running. Then again, write whatever code is needed.
Option 3 - Create a UDF on your user form. Add this field to the Lookup.USR_PROCESS_TRIGGERS. When your first task completes, use the APIs to update this field with a new value, perhaps the current date. On your AD Process Definition, create a task with the name you used in the lookup. This task will get triggered whenever the field is updated. Now if the user does not have an AD Instance, you don't have to worry about it ever running.
I'm sure you could create other event handlers as well to do this, it just depends on how creative you want to be.
-Kevin

Retrying a particular failed Process Task for all the OIM Users

Hi,
We are using OIM 11.1.1. On a particular day one of the systems was unavailable hence all the process tasks for that system failed for a number of users. Is there any way of viewing all the failed process task and retrying them together, there are over 3000 users and it is not possible to go through them one by one.
Any method either through the console or doing it programatically would be very helpful.
Thanks in advance.
UZ

The OTI table has all the rejected task information. You can use it to link to user and resource instances through the OIU table as well.
You can then take the SCH_KEY and then use code like this to process them:
public void completeTask(){
long[] task = new long[] {123123,3242134,23432,43534,34656,456456};
int counter = 0;
for (long key:task){
try {
counter++;
provIntf.retryTask(key);
System.out.println(counter + "|" + task.length);
} catch (Exception e) {
-Kevin

Update UDF from APIs in process task

Hi,
OIM 11g here. I need to write a task which updates a UDF. How should i do this? I am looking at APIs task but how would i pass the map and resultset through the design console to the method updateUser?
thx in advance
Edited by: Prorad on Dec 3, 2010 7:41 AM

You can instantiate an API like this :
(tcUserOperationsIntf) tcUtilityFactory.getUtility(dataProvider, "Thor.API.Operations.tcUserOperationsIntf");
userInfoMap.put( "Users.User ID", "ABC001");
UserUpdateMap.put("Users.First Name","SUREN")
logger.debug(className, methodName, "Searching For User !!");
tcResultSet userSet = userOper.findAllUsers( userInfoMap );
if ( ( userSet != null ) && userSet.getRowCount() > 0 ) {
userOper.updateUser(userSet, UserUpdateMap);
Thanks
Suren
Edited by: Suren.Singh on Dec 3, 2010 9:12 PM
Edited by: Suren.Singh on Dec 3, 2010 9:13 PM

OIM Update User Details API call.

Hi All,
Can anyone plz provide me the sample API code to update the user details in OIM.
Thanks
Siva

what exactly u wanna see in the code. it is simple as others api calls
you have to pass a hashmap as aparameter.
Map userdata = new HashMap();
userdata.put("Users.First Name", "ABC");
userintf.updateuser(userdata);

Geeting Cluster Node through API Call

Dear All
I am facing a problem in Netweaver 7.0 I have to find out through API as which cluster node the dispatcher is forwarding the requests to. Is there any way of knowing thourgh API calls.
We are using Java as a programming language
Thanks in advance

Ok, here is the update:
We have looked into this issue and we can reproduce it.
I will log a bug on my side but there is a workaround.
Please ask him to use, POST https://api.share.acrobat.com/webservices/api/v1/dc/[nodeid/]?method=move&newname=foo.txt

Trigger another Process Task after Enable User completed

I would like to have a process task trigger after the "Enable User" process task successfully completed.
E.g. Scenario
A user currently has a disabled resource. When I enable the user, the Enable User process task
gets called and enables the user. After that I would like to have my custom process task triggered after that.
I tried adding my custom process task in the Enable User task as a dependent task, but it never gets called.
Also, I tried adding the custom task to Tasks to Generate but that did not work.
What am I doing wrong or am I missing a step?

Instructions:
Goal: When 1st process task is triggered, the 2nd process task will kickoff.
1. Select the 1st process task
2. In the Task Dependency Tab of the 1st process task, add the 2nd process task in the Dependant Task section.
3. In the Responses Task of the 1st process task, select the SUCCESS response and add the 2nd process task in the Tasks to Generate section.
IMPORTANT: Each response has its own Task to Generate. So make sure you add to the response you want the 2nd process task to trigger off by.

How to catch rollback in Disable user process task in Xellerat User Process

hi ...
I want to send an email to manager group of the user, once the user is disabled from the OIM (when end date is reached). I created an adapter and attached it to the ‘Changed User Disabled’ process task in the ‘xellerate user provisioning’ process and add a new row in the “Lookup.USR_PROCESS_TRIGGERS” Lookup definition. (code key: USR_DISABLED and Decode: Change User Disabled ). This adapter executes only when the user status is equal to “disabled”.
This works correctly when the OIM user disabling process execute without any errors. But sometimes while disabling the user it gives an error (“resource is not configured properly”) and rolls back everything and make the user active. But at the same time my adapter runs and sends the mail informing user is disabled but yet user is active.
My problem is how can I find or catch rolls back transaction in the “Disable User” process task (which is in “Xellerate User” process”) ??? If I can get to know that a roll back is occurred then I can send a mail to OIM administrator, informing that user disable process is failed.
Can someone please help me to find this..
Thanks in advance :)
Regards,
i.k.

Hi Rajiv,
Error occurs while disabling the user due to resource configuration problems. ( error message is : DOBJ.RESOURCE_NOTCONFIGURED_PROPERLY -- One or more provisioned resource is not configured properly) In this case i know the problem and how to solve it. But what I want to know is in any case if disable process get fail and if things get roll back again, then how can I track that situation and send a mail to OIM Admin(informing the failure) instead of sending a mail to user managers saying that user account has been disabled.
I think now my problem is clear…. Can u please help me to find this.
Regards,
i.k.

Can we add process tasks to Xellerate User process?

Hi,
Can I add a process task- unconditional one to "Xellerate User" process definition?
I want certain fields to be populated in User Profile Form, when the user is created/updated.
Please advice

I could manage to trigger the Xellerate User Process Task and it runs fine, but when trying to update the OIM user field, it throws the below error:
oracle.iam.platform.authz.exception.AccessDeniedException: You do not have permission to modify the [USR_UDF_IPWD] attributes of the user with user key null.
at oracle.iam.identity.usermgmt.impl.UserManagerImpl.modify(UserManagerImpl.java:830)
at oracle.iam.identity.usermgmt.impl.UserManagerImpl.modify(UserManagerImpl.java:971)
usrManager.modify("User Login",sUserLogin.toString().toUpperCase(), new User(null, usrDetails));
usDetails hashmap contains the key, value pair which needs to be updated.

User Exits for Inbound Process

hi all
can any one please give some example user exits in inbound process and explain the omportance of user exits
Thank you,
Swapna

hi
Userxits allow us to add our own functionality to SAP standard program
without modifying it . These are implemented in the form of subroutines and hence are also known as FORM EXITs. The userexits are generally collected in includes and attached to the standard program by the SAP.
Types of User exits
1. Menu Exits
2.Function exits
3.Table exits
4.Screen exits
5.Keyword exits
6.Field exits.
also refer to the links below.. can get more info on user exits
list of user exits
http://www.planetsap.com/userexit_main_page.htm
can also get the list of user exits thru..
Tcode: CMOD -> Utilities -> SAP Enhancements -> F8 Execute
User Exits Notes:
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://help.sap.com/saphelp_nw04/helpdata/en/81/8c5738ee806b0ee10000009b38f889/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
below are some of the useful invound and outbound userexits
<b>IDoc Inbound User Exits</b>
1.     ACC_BILLING
Accounting: Post invoice (OAG: LOAD RECEIVABLE)
     ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
2.     ACC_EMPLOYEE_EXP
FI/CO: HR posting GL (AcctngEmplyeeExenses)
     ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
3.     ACC_EMPLOYEE_PAY
FI/CO: HR posting AP (AcctngEmplyeePaybles)
     ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
4.     ACC_EMPLOYEE_REC
FI/CO: HR posting AR (AcctngEmplyeeRcvbles)
     ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
5.     ACC_GL_POSTING
Accounting: General G/L account posting
     ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
6.     ACC_GOODS_MOVEMENT
Accounting: Post goods movement (OAG: POST JOURNAL)
     ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
7.     ACC_INVOICE_RECEIPT
Accounting: Post invoice receipt (OAG: LOAD PAYABLE)
     ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
8.     ACLPAY Accounting: Inbound invoice
     ACCID001 EXIT_SAPLACC1_031 IDoc ACLPAY: Userexit for creditor in accounting document
     ACCID001 EXIT_SAPLACC1_032 IDoc ACLPAY: Userexit for GL posting in accounting document
     ACCID001 EXIT_SAPLACC1_033 IDoc ACLPAY: Userexit for taxes in accounting document
9.     ACLREC
Accounting: Billing document
     ACCID001 EXIT_SAPLACC1_011 IDoc ACLREC: Userexit for debitor in accounting document
     ACCID001 EXIT_SAPLACC1_012 IDoc ACLREC: Userexit for GL posting in accounting document
     ACCID001 EXIT_SAPLACC1_013 IDoc ACLREC: Userexit for taxes
10.     ACPJMM
Posting in accounting from materials management
     ACCID001 EXIT_SAPLACC1_021 IDoc ACPJOU: Userexit for GL posting in accounting document
11.     ARTMAS
Create and change of material master (Retail)
     MGV00003 EXIT_SAPL1001_003 Enhancement for article master: IDoc inbound
12.     BLAOCH
Purchasing contract change
     MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
     MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
     MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
13.     BLAORD
Purchasing contracts
     MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
     MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
     MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
14.     BLAREL
Release order documentation for distributed contracts
     MM06E001 EXIT_SAPLEINM_004 Customer enhancements for release documentation inbound
15.     COND_A
Conditions: master data for price determination
     VKOI0001 EXIT_SAPLVKOI_001 Interchange of Conditions: Inbound Processing Modifications E1KOMG Segment
     VKOI0001 EXIT_SAPLVKOI_002 Interchange of Conditions: Inbound Processing Customer Segments
16.     CREMAS
Distribute vendor master
     VSV00001 EXIT_SAPLKD02_001 Inbound: Read and process vendor segments
17.     DEBMAS
Customer master
     VSV00001 EXIT_SAPLVV02_001 Inbound: Read and update additional customer master segments
18.     DELINS
Delivery schedule/JIT schedule
     VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
     VED40001 EXIT_SAPLVED4_002 Copying Data to Screens for Incoming EDI Docs
     VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
     VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
19.     DESADV
Delivery: Shipping notification
     LMELA010 EXIT_SAPLEINM_010 Customer enhancement shipping notification inbound: line item
     MM06E001 EXIT_SAPLEINM_006 Customer enhancements for shipping notification inbound
     V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
     V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
     V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
     V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
     V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
     V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
20.     DOCMAS
Master document
     CVDS0001 EXIT_SAPLCVALE_001 Userexit for ALEDVS (DOCMAS inbound)
21.     DOLMAS
Document-object links
     CVDS0001 EXIT_SAPLCVALE_003 Userexit for ALEDVS (DOLMAS inbound)
22.     EDLNOT
EDL delivery notes
     VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
     VED40001 EXIT_SAPLVED4_002 Copying Data to screens for Incoming EDI Docs
     VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
     VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
23.     FIDCC1
Send entire FI documents (user exit 003/4)
     F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
     F050S002 EXIT_SAPLF050_004 FIDCC1 IDoc inbound: Change IDoc / do not process
     F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
     F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
24.     FIDCC2
Send entire FI documents (user exit 005/6)
     F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
     F050S003 EXIT_SAPLF050_006 FIDCC2 IDoc inbound: Change IDoc / do not process
     F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
     F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
25.     FIDCMT
Sending single items for FI-GL
     F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
     F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
26.     FINSTA
Bank Statement
     FEDI0005 EXIT_SAPLIEDP_201 FI-EDI: inbound - bank statement/ Lockbox - Final processing
     FEDI0005 EXIT_SAPLIEDP_202 FI-EDI: inbound - bank statement/ Lockbox - Processing of segments
27.     FIROLL
General ledger rollup for FI-GL (delta f. line items FIDCMT)
     F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
28.     GSVERF
Cred. memo procedure
     VED50001 EXIT_SAPLVED5_001 User Exit for Condition Value Tolerances in the Self- Billing Procedure
     VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
     VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
29.     HRMD_A
HR: Master data and organizational data (appl. system)
     RHALE001 EXIT_SAPLRHA0_002 HR-CA: ALE inbound processing: Export parameter
     RHALE001 EXIT_SAPLRHAL_002 HR-CA: ALE inbound processing: Change info type data
     RHALE001 EXIT_SAPLRHAL_004 HR-CA: ALE inbound processing: conversion segment/ info type
30.     INFREC
Purchasing info record
     MMAL0004 EXIT_SAPLMEAI_004 ALE source list distribution: inbound processing userdefined data
     MMAL0004 EXIT_SAPLMEAI_003 ALE purchasing info record distribution: inbound processing segments
31.     INVOIC
Invoice / Billing document
     FEDI0001 EXIT_SAPLIEDI_001 FI-EDI: Invoice receipt - Determine G/L account per invoice line
     FEDI0001 EXIT_SAPLIEDI_002 FI-EDI: Invoice receipt - Determine add. acct assignm. per line item
     FEDI0001 EXIT_SAPLIEDI_003 FI-EDI: Invoice receipt - Fill the screen field 'Allocation'
     FEDI0001 EXIT_SAPLIEDI_004 FI-EDI: Invoice receipt - Determine the segment text
     FEDI0001 EXIT_SAPLIEDI_005 FI-EDI: Invoice receipt - Determine the name of the BDC session
     FEDI0001 EXIT_SAPLIEDI_011 MM-EDI: Invoice receipt - Determine purchase order item
     FEDI0001 EXIT_SAPLIEDI_101 FI-EDI: Invoice receipt INVOIC01 - additional assignment
     FEDI0001 EXIT_SAPLIEDI_102 FI-EDI: Invoice receipt INVOIC01 - add data
     FEDI0001 EXIT_SAPLIEDI_111 MM-EDI: Invoice receipt INVOIC01 - additional assignment
     FEDI0001 EXIT_SAPLIEDI_112 MM-EDI: Invoice receipt INVOIC01 - add data
     MRMH0002 EXIT_SAPLMRMH_011 Logistics Invoice Verification:inboud EDI message, company code
     MRMH0002 EXIT_SAPLMRMH_012 Logistics Invoice Verification:inboud EDI message, control flags
     MRMH0002 EXIT_SAPLMRMH_013 Logistics Invoice Verification:inboud EDI message, assignment
     MRMH0002 EXIT_SAPLMRMH_014 Logistics Invoice Verification:inboud EDI message, segments
     MRMH0002 EXIT_SAPLMRMH_015 Logistics Invoice Verification:inbound EDI message, before posting
32.     LIKOND
Listing conditions
     WSOR0001 EXIT_SAPLWSOI_001 Enhancement for assortments: inbound IDoc
33.     MATMAS
Material Master
     MGV00001 EXIT_SAPLMV02_002 Enhancement for material master IDoc: Update
34.     MRESCR
Create reservation
     SAPLMEWB EXIT_SAPLMEWB_001 Customer exit for processing of reservations via BAPIs
35.     ORDCHG
Purchase order/order change
     MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
     MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
     VEDB0001 EXIT_SAPLVEDB_001 SD EDI incoming change orders: read additional data from IDoc
     VEDB0001 EXIT_SAPLVEDB_002 SD EDI incoming change orders: additional data for dynpros
     VEDB0001 EXIT_SAPLVEDB_003 SD EDI incoming change orders: further activities after calling
     VEDB0001 EXIT_SAPLVEDB_004 SD EDI incoming change orders: closing activities per
     VEDB0001 EXIT_SAPLVEDB_005 SD EDI incoming change orders: closing activities by order block
     VEDB0001 EXIT_SAPLVEDB_006 SD EDI incoming change orders: setting order type
     VEDB0001 EXIT_SAPLVEDB_007 SD EDI incoming change orders: additional checks of IDoc
     VEDB0001 EXIT_SAPLVEDB_008 SD EDI incoming change orders: error handling
     VEDB0001 EXIT_SAPLVEDB_009 SD EDI incoming change orders: additional checks of IDoc segments
     VEDB0001 EXIT_SAPLVEDB_010 SD EDI incoming change orders: manipulation of status ecords
     VEDB0001 EXIT_SAPLVEDB_012 SD EDI incoming change orders: change internal table
36.     ORDERS
Purchase order / order
     MCP20008 EXIT_SAPLMCP2_008 User exit: Processing of purchase order header
     MCP20008 EXIT_SAPLMCP2_009 User exit: Processing of purchase order item
37.     ORDERS
Purchase order / order
     MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
     MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
     VEDA0001 EXIT_SAPLVEDA_001 SD EDI incoming orders: read additional data from IDoc
     VEDA0001 EXIT_SAPLVEDA_002 SD EDI incoming orders: additional data for dynpros
     VEDA0001 EXIT_SAPLVEDA_003 SD EDI incoming orders: further activities after calling
     VEDA0001 EXIT_SAPLVEDA_004 SD EDI incoming orders: closing activities per order
     VEDA0001 EXIT_SAPLVEDA_005 SD EDI incoming orders: closing activities by order block
     VEDA0001 EXIT_SAPLVEDA_006 SD EDI incoming orders: setting order type
     VEDA0001 EXIT_SAPLVEDA_007 SD EDI incoming orders: number of ordering party
     VEDA0001 EXIT_SAPLVEDA_008 SD EDI incoming orders: error handling
     VEDA0001 EXIT_SAPLVEDA_009 SD EDI incoming orders: additional checks of IDoc segments
     VEDA0001 EXIT_SAPLVEDA_010 SD EDI incoming orders: manipulation of status records
     VEDA0001 EXIT_SAPLVEDA_011 SD EDI incoming orders: change internal table
     WVFB0001 EXIT_SAPLWVFB_002 Customer exists for store order PO confirmationdata seg.
38.     ORDRSP
Purchase order / order confirmation
     MM06E001 EXIT_SAPLEINM_005 Customer enhancements for order confirmation inbound
     MM06E001 EXIT_SAPLEINM_007 Customer enhancements inbound confirmation: reading
     MM06E001 EXIT_SAPLEINM_008 Customer enhancements inbound confirmation: final
     WVMI0001 EXIT_SAPLWVMI_003 ORDRSP VMI inbound, modification before creating purchase order
39.     PORDCR
Create purchase order
     SAPLMEWP EXIT_SAPLMEWP_002 Customer exit for processing of purchase orders via BAPIs
40.     PREQCR
Create purchase requisition
     SAPLMEWQ EXIT_SAPLMEWQ_001 Customer exit for processing of requisitions via BAPIs
41.     PROACT
Stock and sales data
     WVMI0001 EXIT_SAPLWVMI_002 IDoc PROACT inbound: prior to processing
42.     REMADV
Payment advice
     FEDI0002 EXIT_SAPLIEDP_101 FI-EDI: Incoming pmnt advice - Extended allocatn of IDOC -> applicatn data
     FEDI0002 EXIT_SAPLIEDP_102 FI-EDI: Incoming pmnt adivce - Closing allocatn of IDOC -> applicatn data
43.     REQOTE
Inquiry
     VEDQ0001 EXIT_SAPLVEDQ_001 SD EDI inbound inquiry: read additional data from IDoc
     VEDQ0001 EXIT_SAPLVEDQ_002 SD EDI inbound inquiry: additional data for dynpros
     VEDQ0001 EXIT_SAPLVEDQ_003 SD EDI inbound inquiry: further activities after calling
     VEDQ0001 EXIT_SAPLVEDQ_004 SD EDI inbound inquiry: closing activities per inquiry
     VEDQ0001 EXIT_SAPLVEDQ_005 SD EDI inbound inquiry: closing activities by inquiry block
     VEDQ0001 EXIT_SAPLVEDQ_006 SD EDI inbound inquiry: setting inquiry type
     VEDQ0001 EXIT_SAPLVEDQ_007 SD EDI inbound inquiry: number of sold-to party
     VEDQ0001 EXIT_SAPLVEDQ_008 SD EDI inbound inquiry: error handling
     VEDQ0001 EXIT_SAPLVEDQ_009 SD EDI inbound inquiry: additional checks of IDoc segments
     VEDQ0001 EXIT_SAPLVEDQ_010 SD EDI inbound inquiry: manipulation of status records
     VEDQ0001 EXIT_SAPLVEDQ_011 SD EDI inbound inquiry: change internal table
44.     SBINV
Credit memo procedure with invoice creation
     VED50001 EXIT_SAPLVED5_002 User Exit for messages in the Self-Billing Procedure SBINV
     VED50001 EXIT_SAPLVED5_003 User Exit for Tolerances in the Self- Billing Procedure SBINV
     VED50001 EXIT_SAPLVED5_004 Customer-Function for changing invoice data SBINV
     VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
     VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
45.     SDPACK
Packing confirmation
     VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling - Inbound IDoc
     VMDE0004 EXIT_SAPLVMDE_004 Shipping Interface: Message SDPACK (Packing, Inbound)
46.     SDPICK
Picking confirmation
     VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling - Inbound IDoc
     VMDE0003 EXIT_SAPLVMDE_003 Shipping Interface: Message SDPICK (Picking, Receipt)
47.     SHP_IBDLV_CONFIRM_DECENTRAL
Confirmation (Inbound Delivery)
     V50B0001 EXIT_SAPLV50I_002 User exit for BAPI Verification of Inbound Deliveries
48.     SHP_IBDLV_SAVE_REPLICA
BAPI Function Module for Duplication of Outbound Deliveries
     V50B0001 EXIT_SAPLV50I_001 User exit for BAPI Duplication of Inbound Deliveries
49.     SHP_OBDLV_CONFIRM_DECENTRAL
Confirmation (Customer Delivery)
     V50B0001 EXIT_SAPLV50I_004 User exit for BAPI Verification of Outbound Deliveries
50.     SHP_OBDLV_SAVE_REPLICA
BAPI Function Module for Duplication of Outbound Deliveries
     V50B0001 EXIT_SAPLV50I_003 User exit for BAPI Duplication of Outbound Deliveries
51.     SHPCON
Delivery: Shipping confirmation
     V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
     V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
     V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
     V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
     V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
     V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
52.     SHPMNT
Shipping outbound
     V55K0020 EXIT_SAPLV55K_020 IDoc SHPMNT: Modification Control/ Data before processing
     V55K0021 EXIT_SAPLV55K_021 Processing of segments IDoc SHPMNT
     V55K0022 EXIT_SAPLV55K_022 Update of user defined tables for inbound IDoc SHPMNT
53.     SRCLST
Source List
     MMAL0002 EXIT_SAPLMEAI_001 ALE source list distribution: inbound processing segments
     MMAL0002 EXIT_SAPLMEAI_002 ALE source list distribution: inbound processing user defined data
54.     SRVMAS
Master data service master
     BASI0001 EXIT_SAPLBASI_001 Userexit IDoc inbound service master: segment
     BASI0001 EXIT_SAPLBASI_002 Userexit IDoc inbound service master: database
55.     TPSSHT
Shipping planning system: Transfer planned shipments
     V56I0010 EXIT_SAPLV56I_010 IDoc TPSSHT01: Input of planned shipments: Modification of IDoc segments
     V56I0010 EXIT_SAPLV56I_011 IDoc TPSSHT01: Input of planned shipments: modification of transport tab, processing
     V56I0010 EXIT_SAPLV56I_012 IDoc TPSSHT01: Input of planned shipments: update of own tables
56.     WHSCON
Delivery: Stock confirmation
     V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
     V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
     V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
     V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
     V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
     V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
57.     WMBBIN
Block Storage Bins
     MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
     MWMIDI04 EXIT_SAPLLIDI_004 Customer enhancement for IDoc WMBBID01
58.     WMCATO
Reversal/Reversal request for transfer order
     MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
     MWMIDI03 EXIT_SAPLLIDI_003 Customer enhancement for IDoc WMCAI01
59.     WMINVE
Inventory count input
     MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
     MWMIDO09 EXIT_SAPLLMDE_003 Customer enhancement for message WMINVE
     MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
60.     WMMBXY
IDoc Report goods movements in IM
     MWMIDO08 EXIT_SAPLLMDE_002 Customer enhancement for message WMMBXY (goods movement) inbound
61.     WMSUMO
Move storage unit
     MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
     MWMIDI06 EXIT_SAPLLIDI_006 Customer enhancement for IDoc WMSUID01
62.     WMTOCO
Transfer order
     MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
     MWMIDI02 EXIT_SAPLLIDI_002 Customer enhancement for IDoc WMTCID01
63.     WMTORD
Transfer order
     MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
     MWMIDO10 EXIT_SAPLLMDE_004 Customer enhancement for message WMTORD (Create TO) inbound
     MWMIDO11 EXIT_SAPLLMDE_005 Customer enhancement for message WMTORD (Create TO) inbound
64.     WMTREQ
Create/Cancel transfer order
     MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
     MWMIDI05 EXIT_SAPLLIDI_005 Customer enhancement for IDoc WMTRID01
65.     WPUBON
POS interface: Upload sales documents (compressed)
     WPUE0002 EXIT_SAPLWPUE_104 IDoc WPUBON01: prior to inbound processing
     WPUE0002 EXIT_SAPLWPUE_105 Check, whether transaction of IDoc WPUBON01 is compressable
     WPUE0002 EXIT_SAPLWPUE_106 IDoc WPUBON01: processing user segment
     WPUE0002 EXIT_SAPLWPUE_109 IDoc WPUBON01: after to inbound processing
66.     WPUFIB
POS interface: Upload Fin.Acc. interface SRS/POS
     WPUE0002 EXIT_SAPLWPUE_130 IDoc WPUFIB01: prior to update
     WPUE0002 EXIT_SAPLWPUE_131 IDoc WPUFIB01: processing user
67.     WPUFIB
POS interface: Upload Fin.Acc. interface SRS/POS
     WPUE0002 EXIT_SAPLWPUE_132 IDoc WPUFIB01: prior to inbound processing
     WPUE0002 EXIT_SAPLWPUE_139 IDoc WPUFIB01: after to inbound processing
68.     WPUKSR
POS upload cashier data
     WPUE0002 EXIT_SAPLWPUE_120 IDoc WPUKSR01: prior to update
     WPUE0002 EXIT_SAPLWPUE_122 IDoc WPUKSR01: processing user segment
     WPUE0002 EXIT_SAPLWPUE_123 IDoc WPUKSR01: prior to inbound processing
     WPUE0002 EXIT_SAPLWPUE_129 IDoc WPUKSR01: after to inbound processing
     WPUE0002 EXIT_SAPLWPUE_152 IDoc WPUTAB01: prior to inbound processing
     WPUE0002 EXIT_SAPLWPUE_159 IDoc WPUTAB01: after to inbound processing
69.     WPUUMS
POS interface: Upload sales data (compressed)
     WPUE0002 EXIT_SAPLWPUE_110 IDoc WPUUMS01: prior to update
     WPUE0002 EXIT_SAPLWPUE_112 IDoc WPUUMS01: prior to inbound processing
     WPUE0002 EXIT_SAPLWPUE_113 IDoc WPUUMS01: processing user segment
     WPUE0002 EXIT_SAPLWPUE_119 IDoc WPUUMS01: after to inbound processing
70.     WPUWBW
POS interface: Upload goods movements
     WPUE0002 EXIT_SAPLWPUE_140 IDoc WPUWBW01: prior to update
     WPUE0002 EXIT_SAPLWPUE_141 IDoc WPUWBW01: processing user segment
     WPUE0002 EXIT_SAPLWPUE_142 IDoc WPUWBW01: prior to inbound processing
     WPUE0002 EXIT_SAPLWPUE_149 IDoc WPUWBW01: after to inbound processing
71.     WVINVE
Store physical inventory / sales price revaluation
     WVFI0001 EXIT_SAPLWVFI_001 Inbound IDoc store phys. inv.: override Customizing
     WVFI0002 EXIT_SAPLWVFI_002 Inbound IDoc store phys. inv.: process customer segment
<b>IDoc Outbound User Exits</b>
72.     ACCONF
Confirmation of IDoc processing from the application
     ACCID002 EXIT_SAPLACC2_040 IDOC ACCONF: Confirmation of processing in application
73.     ACLPAY
Accounting: Inbound invoice
     ACCID002 EXIT_SAPLACC2_030 IDoc ACLPAY: Userexit for header in accounting document (outbound)
     ACCID002 EXIT_SAPLACC2_031 IDoc ACLPAY: Userexit for creditor line (outbound) in accounting document
     ACCID002 EXIT_SAPLACC2_032 IDoc ACLPAY: Userexit for general line (outbound) in accounting document
     ACCID002 EXIT_SAPLACC2_033 IDoc ACLPAY: Userexit for tax line (outbound) in accounting document
74.     ACPJMM
Posting in accounting from materials management
     ACCID002 EXIT_SAPLACC2_020 IDoc ACPJOU: Userexit Userexit for GL posting header in accounting document
     ACCID002 EXIT_SAPLACC2_021 IDoc ACPJOU: Userexit Userexit for GL posting line in accounting document
75.     ARTMAS
Create and change of material master (Retail)
     MGV00003 EXIT_SAPLMV01_003 Enhancement for article master IDoc: Create
76.     BLAORD
Purchasing contracts
     MM06E001 EXIT_SAPLEINM_016 ALE distribution of contracts outbound enhancement for IDocs
     MM06E001 EXIT_SAPLEINM_017 ALE distribution of contracts outbound enhancement for IDocs
77.     BLAREL
Purchasing contracts
     MM06E001 EXIT_SAPLEINM_003 Customer enhancements of data segment for outbound release documentation
78.     COND_A
Conditions: master data for price determination
     VKOE0001 EXIT_SAPLVKOE_001 Condition Transmission: Derivation of Filter Object E1KOMG
     VKOE0001 EXIT_SAPLVKOE_002 Condition Transmission: Customer segments
79.     CREMAS
Distribute vendor master
     VSV00001 EXIT_SAPLKD01_001 Outbound: Create vendor segments
80.     DEBMAS
Customer master
     VSV00001 EXIT_SAPLVV01_001 Outbound: Create additional customer master segments
81.     DELPKB
KANBAN call
     MPKD0001 EXIT_SAPLMPKD_001 User exit for control record KANBAN, outbound
     MPKD0001 EXIT_SAPLMPKD_002 User exit for EDI
82.     DIRDEB
Preauthorized withdrawal
     FEDI0003 EXIT_SAPLIEDP_003 FI-EDI outgoing payments: Save PEXR segments (customer directory)
83.     DOCMAS
Master document
     CVDS0001 EXIT_SAPLCVALE_002 Userexit for ALEDVS (DOCMAS outbound)
     CVDS0001 EXIT_SAPLCVALE_005 Userexit for filter (ALE outbound)
84.     DOLMAS
Document-object links
     CVDS0001 EXIT_SAPLCVALE_004 Userexit for ALEDVS (DOLMAS outbound)
     CVDS0001 EXIT_SAPLCVALE_005 Userexit for filter (ALE outbound)
85.     FIDCC1
Send entire FI documents (user exit 003/4)
     F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
     F050S002 EXIT_SAPLF050_003 FIDCC1 IDoc outbound: Change data / do not send
     F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
86.     FIDCC2
Send entire FI documents (user exit 005/6)
     F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
     F050S003 EXIT_SAPLF050_005 FIDCC2 IDoc outbound: Change data / do not send
     F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
     F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
87.     FIDCMT
Sending single items for FI-GL
     F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
88.     FIPAYM
Payment data
     FIPAYM01 EXIT_SAPLF11A_001 USER-EXIT: message type FIPAYM, header data, outbound
     FIPAYM01 EXIT_SAPLF11A_002 USER-EXIT: message type FIPAYM, reference data, outbound
     FIPAYM01 EXIT_SAPLF11A_003 USER-EXIT: message type FIPAYM, bank data, outbound
     FIPAYM01 EXIT_SAPLF11A_004 USER-EXIT: message type FIPAYM, GL data, outbound
     FIPAYM01 EXIT_SAPLF11A_005 USER-EXIT: message type FIPAYM, partner data, outbound
89.     FIROLL
General ledger rollup for FI-GL (delta f. line items FIDCMT)
     F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
90.     GSVERF
Cred. memo procedure
     MRMN0001 EXIT_SAPLMRMN_001 Outbound IDoc for ERS/consignment settlement
91.     HRMD_A
HR: Master data and organizational data (appl. system)
     RHALE001 EXIT_SAPLRHA0_001 HR-CA: ALE outbound processing: Enhancement for receiver
     RHALE001 EXIT_SAPLRHAL_001 HR-CA: ALE outbound processing: Change IDoc
     RHALE001 EXIT_SAPLRHAL_003 HR-CA: ALE outbound processing: conversion info type / segment
92.     INFREC
Purchasing info record
     MMAL0003 EXIT_SAPLMEAO_002 ALE purchasing info record distribution: outbound processing
93.     INVOIC
Invoice / Billing document
     LVEDF001 EXIT_SAPLVEDF_001 User_Exit controll data IDoc_Output_Invoic
     LVEDF001 EXIT_SAPLVEDF_002 User_Exit customer enhancement of segments outbound invoice
     LVEDF001 EXIT_SAPLVEDF_003 User_Exit to avoid reading package data
     LVEDF001 EXIT_SAPLVEDF_004 EDI Invoice: customer enhancement for reading additional data
94.     KANBAN
KANBAN call
     MPKD0001 EXIT_SAPLMPKD_001 User exit for control record KANBAN, outbound
     MPKD0001 EXIT_SAPLMPKD_002 User exit for EDI
95.     LIKOND
Listing conditions
     WSOR0001 EXIT_SAPLWSOE_001 Enhancement for assortments: outbound IDoc
96.     MATMAS
Material Master
     MGV00001 EXIT_SAPLMV01_002 Enhancement for material master IDoc: Create
97.     ORDCHG
Purchase order/order change
     MM06E001 EXIT_SAPLEINM_001 Customer enhancements for control record: purchasing document, outbound
     MM06E001 EXIT_SAPLEINM_002 Customer enhancements to data segments, purchasing document, outbound
     MM06E001 EXIT_SAPLEINM_011 Final customer enhancement EDI purchase order outbound
98.     ORDERS
Purchase order / order
     MM06E001 EXIT_SAPLEINM_001 Customer enhancements for control record: purchasing document, outbound
     MM06E001 EXIT_SAPLEINM_002 Customer enhancements to data segments, purchasing document, outbound
     MM06E001 EXIT_SAPLEINM_011 Final customer enhancement EDI purchase order outbound
99.     ORDRSP
Purchase order / order confirmation
     MM06E001 EXIT_SAPLEINM_009 MM EDI ORDRSP: customer enhancements tolerances (quantities/ date/price)
     MM06E001 EXIT_SAPLEINM_014 MM EDI ORDRSP:enhancement price tolerances
     MM06E001 EXIT_SAPLEINM_015 MM EDI ORDRSP: enhancement change of vendor material
     SDEDI001 EXIT_SAPLVEDC_001 Customer enhancement for control record of order confirmation
     SDEDI001 EXIT_SAPLVEDC_002 Customer enhancement for data records of order confirmation
     SDEDI001 EXIT_SAPLVEDC_003 SD EDI ORDRSP: customer enhancement
     SDEDI001 EXIT_SAPLVEDC_004 SD EDI ORDRSP:customer enhancement for reading additional data
     SDEDI001 EXIT_SAPLVEDC_005 SD EDI ORDRSP: customer enhancement for configuration
     SDEDI001 EXIT_SAPLVEDC_006 SD EDI ORDRSP: customer enhancement for configuration structures
     SDEDI001 EXIT_SAPLVEDC_007 SD EDI ORDRSP: customer enhancement for header conditions
     SDEDI001 EXIT_SAPLVEDC_008 SD EDI ORDRSP: customer enhancement for item conditions
     WVFB0001 EXIT_SAPLWVFB_001 Customer exists for store order PO confirmation control seg.
     WVFB0001 EXIT_SAPLWVFB_003 Customer exists for store order PO confirmation data seg.
100.     PAYEXT
Extended payment order
     FEDI0003 EXIT_SAPLIEDP_002 FI-EDI outgoing payments: Save PEXR segments (external payments)
     FEDI0004 EXIT_SAPLIEDP_901 FI-EDI outgoing payments: New partner house bank
     FEDI0004 EXIT_SAPLIEDP_902 FI-EDI outgoing payments: End of IDoc payment (VBLNR)
     FEDI0004 EXIT_SAPLIEDP_903 FI-EDI outgoing payments: End of partner house bank
101.     PICKSD
Picking data confirmation to customer delivery
     VMDE0002 EXIT_SAPLVMDE_002 Shipping Interface: Message PICKSD (Picking, Outbound)
102.     PRDCAT
Product Catalog
     WPCI0001 EXIT_SAPLWPCI_001 User exit for Product cat. IDoc outbound
103.     PRDPOS
Product catalog item
     WPCI0001 EXIT_SAPLWPCI_001 User exit for Product cat. IDoc outbound
104.     PRICAT
Price list / catalog
     VPRE0001 EXIT_SAPLVPRE_001 PRICAT outbound processing (MAMT AUSP MAW1)
     VPRE0001 EXIT_SAPLVPRE_002 PRICAT outbound processing (control record)
     VPRE0001 EXIT_SAPLVPRE_003 PRICAT outbound processing (IDoc segments)
105.     PROACT
Stock and sales data
     WVMI0001 EXIT_SAPLWVMI_001 IDoc PROACT outbound: final action prior to sending
106.     REMADV
Payment advice
     FEDI0003 EXIT_SAPLIEDP_001 FI-EDI: Outgoing pmnt advice - Create extension of segments/ new segments
107.     REQOTE
Inquiry
     VEDE0001 EXIT_SAPLVEDE_001 Customer enhancement for control record of outbound quotation
     VEDE0001 EXIT_SAPLVEDE_003 SD EDI REQOTE: customer enhancement
     VEDE0001 EXIT_SAPLVEDE_002 Customer enhancement for data records of outbound quotation
     VEDE0001 EXIT_SAPLVEDE_004 SD EDI REQOTE: customer enhancement for reading additional data
     VEDE0001 EXIT_SAPLVEDE_005 SD EDI REQOTE: customer enhancement for configuration
     VEDE0001 EXIT_SAPLVEDE_006 SD EDI REQOTE: customer enhancement for configuration structures
     VEDE0001 EXIT_SAPLVEDE_007 SD EDI REQOTE: customer enhancement for header conditions
     VEDE0001 EXIT_SAPLVEDE_008 SD EDI REQOTE: customer enhancement for item conditions
108.     SRCLST
Source List
     MMAL0001 EXIT_SAPLMEAO_001 ALE source list distribution: outbound processing
109.     SRVMAS
Master data service master
     BASO0001 EXIT_SAPLBASO_001 Enhancement: service master, check standard service catalog
     BASO0001 EXIT_SAPLBASO_002 Userexit IDoc service master: receiver determination
110.     SYPART
Partner profiles
     SIDOC002 EXIT_SAPLEDI6_001 CA-EDI, Partner-IDoc: Exit after segment E1EDPP1
     SIDOC002 EXIT_SAPLEDI6_002 CA-EDI, Partner-IDoc: Exit after segment E1ADRM0
     SIDOC002 EXIT_SAPLEDI6_003 CA-EDI, Partner-IDoc: Final exit before sending
     SIDOC002 EXIT_SAPLEDI6_004 CA-EDI, Partner-IDoc: Exit after segment E1ADRP0
     SIDOC002 EXIT_SAPLEDI6_005 CA-EDI, Partner-IDoc: Exit after segment E1ADRE0
     SIDOC002 EXIT_SAPLEDI6_007 CA-EDI, Partner-IDoc: Exit after segment E1EDP13
     SIDOC002 EXIT_SAPLEDI6_008 CA-EDI, Partner-IDoc: Exit after segment E1EDP21
111.     TPSDLS
Shipping planning system: Transfer delivery
     V56I0001 EXIT_SAPLV56I_001 IDoc TPSDLS: Modification of delivery header group
     V56I0002 EXIT_SAPLV56I_002 IDoc TPSDLS: Modification of delivery item group
     V56I0003 EXIT_SAPLV56I_003 IDoc TPSDLS: Modification of package data group
     V56I0004 EXIT_SAPLV56I_004 IDoc TPSDLS: Modification of entire IDoc
     V56I0005 EXIT_SAPLV56I_005 IDoc TPSDLS: Modif. of delivery items relevant to shipment
     V56I0006 EXIT_SAPLV56I_006 IDOC TPSDLS: User-defined determ. for location substitution
     V56I0020 EXIT_SAPLV56I_020 IDoc control record modification in interface SD-TPS
112.     WBBDLD
Assortment list: Material data
     WBBE0001 EXIT_SAPLWBBI_001 Modification of replenishment list IDoc
113.     WMCATO
Reversal/Reversal request for transfer order
     MWMIDO02 EXIT_SAPLLIDO_002 Customer enhancement for IDoc WMCAID01
114.     WMINVE
Inventory count input
     MWMIDO04 EXIT_SAPLLIDO_004 Customer enhancement for IDoc WMIVID01
115.     WMRREF
Release reference number
     MWMIDO03 EXIT_SAPLLIDO_003 Customer enhancement for IDoc WMRRID01
116.     WMTORD
Transfer order
     MWMIDO01 EXIT_SAPLLIDO_001 Customer enhancement for IDoc WMTOID01
117.     WP_EAN
POS interface: Upload / Download EAN assignments
     WPDA0001 EXIT_SAPLWPDA_003 POS interface: Modification of IDoc data for EAN references
118.     WP_PER
POS interface: Upload / Download person data
     WPDA0001 EXIT_SAPLWPDA_008 POS interface: Modification of IDoc data for person related data
     WPDA0001 EXIT_SAPLWPDA_013 POS interface: Add. Change pt. Analysis for WP_PER
119.     WP_PLU
POS interface: Upload / Download material master
     WPDA0001 EXIT_SAPLWPDA_002 POS interface: Modification of IDoc data for material master
     WPDA0001 EXIT_SAPLWPDA_009 POS interface: Add. Change pt. Analysis for WP_PLU
120.     WPDCUR
POS interface: Download exchange rates
     WPDA0001 EXIT_SAPLWPDA_006 POS interface: Modification of IDoc data for exchange rates
121.     WPDNAC
POS interface: Download products
     WPDA0001 EXIT_SAPLWPDA_005 POS interface: Modification of IDoc data for follow-on items
     WPDA0001 EXIT_SAPLWPDA_011 POS interface: Add. Change pt. Analysis for WPDNAC
122.     WPDSET
POS interface: Download set assignments
     WPDA0001 EXIT_SAPLWPDA_004 POS interface: modification of IDoc data for set assignments
123.     WPDSET
POS interface: Download set assignments
     WPDA0001 EXIT_SAPLWPDA_010 POS interface: Add. Change pt. Analysis for WPDSET
124.     WPDTAX
POS interface: Download tax rates
     WPDA0001 EXIT_SAPLWPDA_007 POS interface: modification of IDoc data for taxes
125.     WPDWGR
POS interface: Download material group master
     WPDA0001 EXIT_SAPLWPDA_001 POS interface: Modification of IDoc data for material groups
     WPDA0001 EXIT_SAPLWPDA_012 POS interface: Add. Change pt. Analysis for WPDWGR
126.     WPUBON
POS interface: Upload sales documents (compressed)
     WPUE0002 EXIT_SAPLWPUE_102 IDoc WPUBON01: prior to update
127.     WTADDI
Additionals
     WTAD0001 EXIT_SAPLWTIP_001 Enhancements to Additionals IDoc
128.     WTADDI_CVB1
Additionals w/o 06
     WTAD0001 EXIT_SAPLWTIP_001 Enhancements to Additionals IDoc
General IDoc User Exits
     ALE00001 EXIT_RBDPROSE_001 Old: exit for converting preproduction system to production
     ALE00001 EXIT_SAPLBD11_001 User exit for the IDOC version changer
     BDMO0001 EXIT_SAPLBDMO_001 Old: Enhancement to the ALE distribution reference model
     KKCD0001 EXIT_SAPFKCIM_001 SAP-EIS: User exit for data compression of sender records (used for IDoc conversion)
     KKCD0001 EXIT_SAPFKCIM_002 SAP-EIS: User exit for data summ. Of summarized records befo (used for IDoc conversion)
===
User exits for Pricing.
1.USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ
2.USEREXIT_PRICING_PREPARE_TKOMP (module pool SAPLV60A, program RV60AFZZ)
3.USEREXIT_FIELD_MODIFICATION
4.USEREXIT_FIELD_MODIFIC_KZWI
5.USEREXIT_FIELD_MODIFIC_KOPF
User exits for Sales order
1USEREXIT_DELETE_DOCUMENT
2USEREXIT_FIELD_MODIFICATION
3.USEREXIT_MOVE_FIELD_TO_VBAK
4.USEREXIT_NUMBER_RANGE
5.USEREXIT_SAVE_DOCUMENT
User exits for billing
1.USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)
2.USEREXIT_ACCOUNT_PREP_KOMPCV
3USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)
4USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB
5.USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
====
Reward if USeful
Thanx & regards
Naren..

How can I grant Application access to a user via API ) programattically

how do I grant access to a portal user from API
I want to grant access to a user from an API, ie I need a
command to grant "SCOTT" access to "EXAMPLE_APP" APPLICATION as
an end user?

Hi,
I am assuming that you have already updated the EUL in the Administrator Edition, correct? If not, open Discoverer Administrator and login to the database you want to connect to. You must use your EUL user name which I assume has already been created and assigned the correct privileges in the database. You will be asked to update your EUL. Follow the prompts.
Once logged into the EUL, go to Tools \ Privileges and find the user that you want to give administrator access to.
Hopefully, this answers your question.
Regards,
Nancy

Execute Process Task Error - Powershell script

I've got a powershell script that is executed through a Execute Process Task that is giving me an error when executed through the Execute Package Utility on a 64bit server.
"c:\windows\system32\windowspowershell\v1.0\powershell.exe" ""& 'C:\CubeArchive\Linked DB to XMLA.ps1'"" at "", The process exit code was "1" while the expected was "0".
Here's the rub:
It runs fine from Visual Studio on that server.
On my local maching (32bit), it runs fine from both Visual Studio and Execute package Utility.
Does anyone have any idea why this is happening?
Thanks,
Jason

Ok - found the problem.
This is the first time that I'm using powershell.
I had set the ExecutionPolicy on that machine to unrestricted from the powershell console beforehand.
But unknown to me, this setting was only applicable to the 32 bit environment.
I set the 64 bit environment to unrestricted and it worked. (I added another Execution Process Task to the package to set this before hand - I only did this once and now can remove it.)
I thought that the setting for powershell would be server wide, I didn't know that there was a distinction of the 32 bit and 64 bit environments.
Thanks,
Jason

Accessing the user management API programmatically

I am looking for the officially supported method that could be used to access the user management API via "curl" for CRX:
There is a user management API described here:
http://sling.apache.org/site/managing-users-and-groups-jackrabbitusermanager.html
However, executing a command on CRX 2.2 such as:
curl -u:admin:admin http://localhost:7402/system/userManager/user.tidy.1.json
Only returns a message indicating that the contents have been redirected (without providing another URL).
Using the Content Explorer in CRX shows the list of users at: /home/users but I am not sure if a curl command could access the user list via that URL.
Any pointers on how this could be done are appreciated. This is for a partner.
Regards,
Blair

I am a co-worker of MorrellJ. I am trying to do a change password request using the Jackrabbit User Manager with the REST URL /system/userManager/user/<username>.changePassword.json. The problem I am having is that this request requires an oldPwd form param in the request. The issue is that when I am trying to do this request it is in response to the user selecting "Forgot Password" so our logic has created a random password which we then email to the user so they can use that the next time they want to login. We need to change that user's password in CRX so they can log in using it next time. Since they haven't logged in there is no session, NOT the problem. THE PROBLEMS, I don't know 1. how to use the userManager to get that user's old password, since /system/userManager/user/<username>.json doesn't appear to return the password and 2. if I could get the old password it most certainly will be encoded, some how, so I will need some decoding algorithm to pass it through in order to get the actual password to set as the oldPwd form param to my change password request. Please let me know if you require any further explanation. Any assistance would be greatly appreciated. Thank you, in advance, for your assistance.
Sincerely,
Mike Sucena
[email protected]

Creating user through ifsmanager

Hi,
I am creating user through ifsmanager.Only if I make them admin enabled they are able to log in to the ifs.
If I dont give them admin privilege they are not able to login into the ifs.
I just want to make an ordinary user with no admin privileges so that he could just log on.
Also he should be able to view only /home folder and nothing else.
Thanx
-Vipul

Vipul,
I suggest you have a quick read of the Admin Guide - in particular starting / configuring / accessing our out-of-the-box protocol servers.
To use the 9iFS/CM SDK FTP server, you will need an FTP client.
To use the 9iFS/CM SDK SMB/NTFS you will need an appropriate SMB client such as that shipped with Windows.
You need to ensure that you have started the servers up, and be aware of the ports they are running.
Please read the admin guide first though :)
Matt.

Disabling user through API call -process task-followed by an Enable User...

Similar Messages

Maybe you are looking for