Step by Step procedure for creation of IDOC

IntroductionThe main objective of an implementation of the SAP R/3 ERP is to group all the functions of the company together, in a single system. But it is very unlikely that this philosophy is applied so strictly.

Indeed, for such various reasons as load-balancing, task segmentation or also risk distribution, it is common to meet with a software landscape with more than one implementation of SAP R/3. It is even more common that these implementations of SAP R/3 run together with other heterogeneous systems, like AS/400 mainframes (IBM iSeries).

To communicate with each other, SAP has designed for R/3 systems its own communication tool: IDocs. These Intermediate Documents are the basis of every interface between R/3 systems. It is even possible, using a middleware EDI system, to have a R/3 system communicate by IDocs on its side, with an open system by XML files on the other side.

1 Structure of an IDoc interface1.1 Structure of an IDoc1.1.1 SegmentA segment is a record, defined as such in the vocabulary of databases. Indeed, as a line of a database, a segment is a sequence of fields of different length. There is no hierarchical structure within a segment, every fields are at the same level.

1.1.2 SectionAn IDoc is made of three sections: control, data and status. Each section is named following the name of the one or many segments that composed it. Thus, the control section contains a single control segment only, the data section contains one or many data segments, the status section contains one or many status segments.

It is important to notice that when exchanging IDocs between systems, whether they are SAP R/3 or not, only control and data sections are sent. Indeed, the status section remains system specific. Nevertheless, the status section is conceptually associated with the IDoc, so it is systematically represented as being a part of the IDoc.

1.1.2.1 Control sectionThe particularity of the control section is that it contains only one single segment. This section represents the header of the IDoc, it contains an identifier of the IDoc, along with data concerning the sender system and the receiver system.

1.1.2.2 Data sectionThe particularity of the data section is that it contains one or many segments which are organized in a hierarchical way. There is a concept of parent segment and of child segment, a concept in which the child segment could not exist if the superior parent segment does not exist in the hierarchy.

This section is the most important, because as it is implied in its name, it is this section which contains the application data to transmit.

1.1.2.3 Status sectionThe particularity of the status section is that it is specific to the system where the IDoc is displayed. Indeed, after its transfer into an other system, the IDoc is actually rebuilt by copy, segment by segment. The status segments only are not transfered: there are specific to each one of the systems.

This status section is composed of one or many status segments. These segments are organized in a sequential way, so that only the last segment has a real importance. In consequence, what is refered as being the IDoc's status is actually copied from the status mentioned in the last segment of the IDoc's status section.

1.2 Structure of a segment1.2.1 Control segmentThe most important fields of the control segment are the following:

IDoc number: number of the IDoc in the local systemDirection: direction of the IDoc, from the point of view of the local system; 1 stands for outbound, 2 for inboundStatus: current status of the IDoc in the local systemBasic type: basic IDoc typeExtension: type of extension, if applicableMessage type: message typeSender or Recipient information: details concerning the sender or the receiverPort: portPartner number: number of logical systemPartn.Type: partner type; most of the time LS which stands for Logical SystemSAP Release: version number of the IDocOutput Mode: output mode; 2 stands for immediate sending, 4 for collected sending

1.2.2 Data segmentThe structure of a data segment depends on the segment type. Each segment type has a different number of fields, each field having a different length.

The only common characteristic between all the segment types is the format of the data. Indeed, every fields of every data segments have the character format, whatever the way the fields are represented in the IDoc display.

1.2.3 Status segmentThe structure of a status segment is the following:

Status: the status reported by the segmentMessage: the text describing the statusThe other fields of the status segment are used to create a message following a SAP standard structure.

1.3 Structure of an interfaceAn interface is made of the following elements:

A view of the distribution model (optional)No, one or many filtersA sending systemA receiving systemA message typeFor outbound interfaces:A port to emit toAn output modeA packet sizeA basic IDoc typeFor inbound interfaces:A process code

1.3.1 View of the distribution modelThe creation of a view in the distribution model is optional. Indeed, it is strictly obligatory only in a case where the application of a filter is necessary.

After the creation of a view in the distribution model, it is possible to distribute this view to the partner system, as it is also possible to generate the partner profiles for this view.

1.3.2 Message type and basic IDoc typeA message type represents the group in which every basic IDoc types must belong. A message type is conceptually the nature of the data transmitted within an IDoc.

For example, the MATMAS message type is related to material master data, Material Master. To this MATMAS message type is associated several basic IDoc types: MATMAS01, MATMAS02, MATMAS03, MATMAS04 et MATMAS05. Each basic IDoc type is able to contain essential data on material master data. MATMAS01 is the first version, each subsequent version increments the sequence number (MATMAS02, etc.) and adds fields comparing with the previous version.

By convention, each basic IDoc type which follows the ascending numbering can not remove a field or change the applicative meaning of a field comparing with the previous version of the basic IDoc type. The standard message types and basic IDoc types in SAP

R/3 respect this convention, and it is preferable to do so for all the new types to be created.

1.3.3 Partner profilesDealing with every interfaces which do not have any filter, only the partner profiles are effective. Indeed, the views of the distribution model are there only to simplify and conceptualize the partner profiles, without replacing them though.

The parameters in the partner profiles are displayed with a reference frame which is the local system. For exemple, the parameters LS / REMSYST / Outbound deal with the outbound interfaces with the REMSYST logical system.

These parameters are different whether they affect an outbound or an inbound interface.

For outbound interfaces:A port to emit toAn output modeA packet sizeA basic IDoc typeFor inbound interfaces:A process code

2 Customizing of an outbound interfaceThis chapter approaches the creation of a new outbound interface entirely specific. It uses no one of the standard SAP R/3 structures.

2.1 Creation of a new message type2.1.1 Creation of a new segment typeLaunch the WE31 transaction (Development segments: Initial screen).

Fill the Segment type field with the value Z1VISTAPM then press F5 (Create).

Fill the Short Description field and add as much lines as wished fields in the segment. For each field, give it a name and a Data Element to refer to.

Save.

2.1.2 Creation of a new basic IDoc typeLaunch WE30 transaction (Develop IDoc Types: Initial Screen).

Fill the Obj. name field with the value ZVISTAPM01 then press F5 (Create).

In the popup window which appears, choose Create new and fill the Description field.

Select the ZVISTAPM01 header line then choose the Create segment... button. In the popup window which appears, fill the fields like the following:

Segm.type: Z1VISTAPMMandatory seg.: [checked]Minimum number: 1Maximum number: 999999

Save.

2.1.3 Creation of a new message typeLaunch the WE81 transaction (Display View "EDI: Logical Message Types": Overview).

Choose the Display -> Change button then the New Entries button.

In the Message type column, type the value ZVISTAPM then in the Short text column type a short description.

Save.

2.1.4 Association of the basic IDoc type to the message typeLaunch the WE82 transaction (Display View "Output Types and Assignment to IDoc Types": Overview).

Choose the Display -> Change button then the New Entries button.

In the Message Type column, type the value ZVISTAPM. In the Basic Type column, type the value ZVISTAPM01. In the Release column, type the value 620.

2.2 Customizing of a new interface2.2.1 Creation of a new distribution model viewLaunch the BD64 transaction (Display Distribution Model).

Press the Switch between display and edit mode button, then the Create model view button.

In the popup window which appears, enter in the Short text field a short description and in the Technical name field the value YVISTAPM.

Place on the newly created entry then press the Add Message Type button.

In the popup window which appears, enter in the Sender field the name of the local logical system, in the Receiver field the name of the receiving logical system and in the Message type field the name of the message type of the interface.

Validate then save.

2.2.2 Distribute the distribution model viewThis step is necessary only if the partner system is a SAP R/3 system. It allows to

centralize the changes to make on the interface. Be careful! The partner profiles also have to be generated and managed in the partner system.

Select the recently created view then choose in the menu Edit / Model view / Distribute. In the popup window which appears, the partner system is already selected, there is no need to make other further selection. Validate.

2.2.3 Generate and manage the partner profilesFrom the distribution model view (BD64 transaction), place on the message type then choose in the menu Environment / Generate partner profiles, or launch the BD82 transaction (Generating partner profile).

Enter in the Model view field the value YVISTAPM, in the Partner system field the value TIBCO, and choose as Output mode the Collect IDocs and transfer radio button. Press the Execute button.

Check the partner profiles. To do so, launch the WE20 transaction (Partner profiles). Select LS / TIBCO / Outbound parmtrs. / ZVISTAPM.

The port should be checked first, because it is not specified at the generation of the partner profiles level, so it is the first port which is selected by default.

If needed, manage the partner profiles then save.

2.3 Creation of an outbound interface program2.3.1 Creation of an IDoc generation programThe following code extract contains everything needed to generate an IDoc from data contained in a table.

FORM F_110_SEND_IDOC.CONSTANTS: C_MESTYP TYPE EDIDC-MESTYP VALUE 'ZVISTAPM', C_DOCTYP TYPE EDIDC-IDOCTP VALUE 'ZVISTAPM01', C_SEGNAM TYPE EDIDD-SEGNAM VALUE 'Z1VISTAPM'.DATA: I_ZVISTA_PM TYPE ZVISTA_PM_T OCCURS 6000, I_EDIDC TYPE EDIDC OCCURS 0, I_EDIDD TYPE EDIDD OCCURS 0, WA_ZVISTA_PM TYPE ZVISTA_PM_T, WA_EDIDC TYPE EDIDC, WA_EDIDD TYPE EDIDD, WA_Z1VISTAPM TYPE Z1VISTAPM, V_OCCMAX TYPE IDOCSYN-OCCMAX, V_NBSEG TYPE I.CLEAR WA_ZVISTA_PM.CLEAR WA_EDIDC.* Save the message type and the basic IDoc type* in the control segmentMOVE C_MESTYP TO WA_EDIDC-MESTYP.MOVE C_DOCTYP TO WA_EDIDC-IDOCTP.

Retrieve the maximum number of segments in the basic IDoc* typeSELECT MIN( OCCMAX ) FROM IDOCSYN INTO V_OCCMAX WHERE IDOCTYP EQ C_DOCTYP AND SEGTYP EQ C_SEGNAM.

Save the whole ZVISTA_PM_T table content* in the I_ZVISTA_PM internal table.SELECT *FROM ZVISTA_PM_TINTO CORRESPONDING FIELDS OF TABLE I_ZVISTA_PM.

Create a data segment for each line of I_ZVISTA_PMLOOP AT I_ZVISTA_PM INTO WA_ZVISTA_PM. MOVE-CORRESPONDING WA_ZVISTA_PM TO WA_Z1VISTAPM. CLEAR WA_EDIDD. MOVE C_SEGNAM TO WA_EDIDD-SEGNAM. MOVE WA_Z1VISTAPM TO WA_EDIDD-SDATA. APPEND WA_EDIDD TO I_EDIDD. CLEAR WA_ZVISTA_PM. CLEAR WA_Z1VISTAPM.ENDLOOP.

Count the number of data segmentsDESCRIBE TABLE I_EDIDD LINES V_NBSEG.

If the number of data segments exceeds the maximum* allowed number, then edit a message in the spool,* then display an error message (quit the program)IF V_NBSEG GT V_OCCMAX. WRITE:/ TEXT-003, V_OCCMAX. MESSAGE E751.ENDIF.

Call the IDoc creation functionCALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' EXPORTING MASTER_IDOC_CONTROL = WA_EDIDC TABLES COMMUNICATION_IDOC_CONTROL = I_EDIDC MASTER_IDOC_DATA = I_EDIDD EXCEPTIONS ERROR_IN_IDOC_CONTROL = 1 ERROR_WRITING_IDOC_STATUS = 2 ERROR_IN_IDOC_DATA = 3 SENDING_LOGICAL_SYSTEM_UNKNOWN = 4 OTHERS = 5.

If there was an error, display a message (quit the* program)IF SY-SUBRC NE 0. MESSAGE E746.ENDIF.ENDFORM.2.3.2 Running of the IDoc sending programThe interface having been customized for a collected mode output, the program created IDoc is not sent immediately to the receiving system. The IDoc stays waiting for processing. It can be viewed in the BD87 transaction (Status Monitor for ALE Messages).

It is possible to press the Process button to send the IDoc which waits for processing. However, if there were several IDocs to be sent in collected mode, pressing the Process button would have sent them one by one instead of sending them in a batch.

Actually, the RSEOUT00 program has to be executed with adequat parameters: Logical message set to the value ZVISTAPM and Output mode set to the value 4.

3 Additional customizings3.1 Filter3.1.1 PrincipleA filter can be put in place on an interface. A filter is always placed at the distribution level (BD64 transaction), on a particular message type.

A filter is a series of values for one or many fields. When this filter is applied on a message, the segments are created only if the filtered fields contain those values.

Example :Filter 1 : field MATNR = "123", "456"; field ATWRT = "FOO1".Basic IDoc type ZIDOC containing a single segment Z1SEG.The segment (MATNR = "123"; ATWRT = "FOO1"; FIELD1 = "VALUE") will be created.The segment (MATNR = "123"; ATWRT = "VAL2"; FIELD1 = "VALUE") will NOT be created.

So a filter acts the following way: for an IDoc segment to be created, each filtered field has to contain one of the set values. It is a logical "OR" between each value of a field and a logical "AND" between each filtered field.

Be careful! If a segment has a field which do not pass the filter, it is deleted. Then, every segments of a lower hierarchical level are deleted too, as the higher hierarchical level segment also if the deleted segment has been set to be mandatory in the basic IDoc type.

A filter is often used to reduce the volume of sent data, because they are not all relevant for the interface to be built.

3.1.2 Customizing3.1.2.1 Creation of an ALE objectFirst of all, an "ALE object" has to be created to be able to filter on it. An object which type will be identical to the Data Element of the field to be filtered has to be created.

Launch the BD95 transaction (Change View "ALE Object Type": Overview).

In the ALE Object Type field, type the value MATNR. In the Table name field, type the value MAKT. In the Field name field, type the value MATNR. A table field which the Data Element is the same like the field to be filtered should be chosen.

Validate then save.

3.1.2.2 Association of an ALE object type to a message typeLaunch the BD59 transaction (Change View "Assignment of Object Type to Message": Overview).

In the popup window which appears, in the Message type field, type the message that should be filtered, ZVISTAPM here, then validate.

Press the New Entries button. In the ALE Object Type field, type the value MATNR. In the Segm.type field, type the value Z1VISTAPM. In the No. field, type the value 1. In the Field field, type the value MATNR.

Validate and save.

3.1.2.3 Creation of the filter in the distribution modelLaunch the BD64 transaction (Display Distribution Model).

Press the Switch between display and edit mode button, develop the previously created YVISTAPM view and double-clic on the No filter set line.

In the popup window which appears, press the Create filter group button. Develop Data filtering then double-clic on Material.

In the popup window which appears, press the Insert row button and type a value for this field. Do it again for all the values to let pass for this field.

Validate twice then save. Here is your new filter active.

3.2 IDoc reduction3.2.1 PrincipleStandard basic IDoc types are often adapted to all imaginable interfaces. However, it sometimes happens that the sent volume is too big compared with the needs. A filter can applied (see above), which represents a dynamical method.

The number of segments or the number of fields in a segment can also be reduced in a static way, while still keeping the structure of the basic IDoc type. Indeed, for all basic IDocs, SAP had envisaged their reduction.

A reduced IDoc has less segments than the basic IDoc, provided that the deleted segments are not mandatory. The segments of a reduced IDoc can also have less fields than the corresponding segments of the basic IDoc.

Dealing with the standard basic IDoc types, their integration function module already takes into account the possibility of a reduction. The advantage to use reduced IDocs seems to be obvious then: to profit from standard functions while reducing the volume of exchanged data.

3.2.2 CustomizingLaunch the BD53 transaction (IDoc Reduction Maintenance: Initial Screen).

In the Reduced message type field, type the value ZVISTAPM_REDUCED, then press the Create button.

In the popup window which appears, type in the Message type reference field the value MATMAS.

Validate. In the next popup window, type a short description for the new reduced message type. Validate.

In the following window, select the segments and the fields needed for the new reduced message type.

Save.

3.3 Integration of an inbound IDoc3.3.1 DevelopmentBelow is the prototype of the function module to develop to integrate an inbound IDoc.

*"Local interface: IMPORTING VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC EXPORTING VALUE(WORKFLOW_RESULT) LIKE BDWF_PARAM-RESULT VALUE(APPLICATION_VARIABLE) LIKE BDWF_PARAM-APPL_VAR VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS TABLES IDOC_CONTRL STRUCTURE EDIDC IDOC_DATA STRUCTURE EDIDD IDOC_STATUS STRUCTURE BDIDOCSTAT RETURN_VARIABLES STRUCTURE BDWFRETVAR SERIALIZATION_INFO STRUCTURE BDI_SER EXCEPTIONS ERROR_MESSAGE3.3.2 CustomizingBelow is the list of transactions to launch in order to associate the integration function module with the corresponding message type.

BD51 (Display View "Characteristics of Inbound Function Modules": Overview)This transaction is used to register a function module as being able to be used for the integration of an inbound IDoc.WE57 (Display View "IDoc: Assignment of FM to Log. Message and IDoc Type": Overview)This transaction is used to associate the previously declared function module to the message type to be integrated.WE42 (Display View "Inbound process code": Overview)This transaction is used to declare the process codes for integration. These are those codes which will be specified at the partner profiles level for inbound interfaces.

Appendices

4.1 Useful transactions for IDocsBD87 : Status Monitor for ALE MessagesSALE : Display ALE CustomizingWE02 : Display IDocWE05 : IDoc ListsWE09 : Search for IDoc in DatabaseWE19 : Test tool4.2 Standard statuses of IDoc4.2.1 Outbound IDocs statusesStatut Description

0 Not used, only R/21 IDoc generated2 Error passing data to port3 Data passed to port OK4 Error within control information of EDI subsystem5 Error during translation6 Translation OK7 Error during syntax check8 Syntax check OK9 Error during interchange handling10 Interchange handling OK11 Error during dispatch12 Dispatch OK13 Retransmission OK14 Interchange Acknowledgement positive15 Interchange Acknowledgement negative16 Functional Acknowledgement positive17 Functional Acknowledgement negative18 Triggering EDI subsystem OK19 Data transfer for test OK20 Error triggering EDI subsystem21 Error passing data for test22 Dispatch OK, acknowledgement still due23 Error during retransmission24 Control information of EDI subsystem OK25 Processing despite syntax error (outbound)26 Error during syntax check of IDoc (outbound)27 Error in dispatch level (ALE service)28 Not used29 Error in ALE service30 IDoc ready for dispatch (ALE service)31 Error - no further processing32 IDoc was edited33 Original of an IDoc which was edited34 Error in control record of IDoc35 IDoc reloaded from archive36 Electronic signature not performed (timeout)37 IDoc added incorrectly38 IDoc archived39 IDoc is in the target system (ALE service)40 Application document not created in target system41 Application document created in target system42 IDoc was created by test transaction

4.2.2 Inbound IDocs statusesStatut Description

50 IDoc added51 Application document not posted52 Application document not fully posted53 Application document posted54 Error during formal application check55 Formal application check OK56 IDoc with errors added57 Test IDoc: Error during application check58 IDoc copy from R/2 connection59 Not used60 Error during syntax check of IDoc (inbound)61 Processing despite syntax error (inbound)62 IDoc passed to application63 Error passing IDoc to application64 IDoc ready to be transferred to application65 Error in ALE service66 IDoc is waiting for predecessor IDoc (serialization)67 Not used68 Error - no further processing69 IDoc was edited70 Original of an IDoc which was edited71 IDoc reloaded from archive72 Not used, only R/273 IDoc archived74 IDoc was created by test transaction

4.3 List of standard basic IDoc typesThe skills of a good IDoc interfaces manager are, for the most, linked to his good knowledge of standard basic IDoc types. This knowledge allows him or her to put in place interfaces very quickly, without having to develop a new specific type.

Basic type Description100_01 Output682_01 Access sequence683_01 Pricing Procedure (only in 40c)684_01 Condition Exclusion Groups685_01 Condition type686A_01 Conditions: Exclusion indicator:ABSEN1 Attendance/Absence in CC1ACCONF01 Confirmation of IDoc processing from the applicationACC_ACT_ALLOC01 Accounting: Post activity allocationACC_ACT_ALLOC02 Accounting: Post activity allocationACC_ACT_ALLOC03 Accounting: Post Activity AllocationACC_ASSET_TRANSFER01 Accounting: Post Acquisition from TransferACC_ASSET_TRANS_ACQ_POST01 Accounting: Post Acquisition from TransferACC_BILLING01 Accounting: Post Billing Document (OAG: LOAD RECEIVABLE)

ACC_BILLING02 Accounting: Post Billing Document (OAG: LOAD RECEIVABLE)ACC_BILLING_REVERSE01 Accounting: Post Billing Doc.Reversal (OAG: LOAD RECEIVABLE)ACC_DOCUMENT01 Accounting: PostingACC_DOCUMENT02 Accounting: PostingACC_DOCUMENT_REVERSE01 Accounting: Post ReversalACC_EMPLOYEE_EXP01 FI/CO: HR Posting GL(AcctngEmplyeeExpnses)ACC_EMPLOYEE_EXP02 FI/CO: HR posting GL(AcctngEmplyeeExpnses)ACC_EMPLOYEE_PAY01 FI/CO: HR Posting AP(AcctngEmplyeePaybles)ACC_EMPLOYEE_PAY02 FI/CO: HR posting AP(AcctngEmplyeePaybles)ACC_EMPLOYEE_REC01 FI/CO: HR Posting AR(AcctngEmplyeeRcvbles)ACC_EMPLOYEE_REC02 FI/CO: HR posting AR(AcctngEmplyeeRcvbles)ACC_GL_POSTING01 Accounting: General G/L Account PostingACC_GL_POSTING_REVERSE01 Accounting: Post General G/L Posting ReversalACC_GOODS_MOVEMENT01 Accounting: Post Goods Movement (OAG: POST JOURNAL)ACC_GOODS_MOVEMENT02 Accounting: Post Goods Movement (OAG: POST JOURNAL)ACC_GOODS_MOV_REVERSE01 Accounting: Post Goods Movement Reversal (Acctng Goods Mvt)ACC_INVOICE_PYMNTBLK01 Accounting: Change TS posting (AcctngInvoiceReceipt)ACC_INVOICE_RECEIPT01 Accounting: Post Invoice Receipt (OAG: LOAD PAYABLE)ACC_INVOICE_RECEIPT02 Accounting: Post Invoice Receipt (OAG: LOAD PAYABLE)ACC_INVOICE_RECEIPT03 Accounting: Post Invoice Receipt (OAG: LOAD PAYABLE)ACC_INVOICE_REVERSE01 Accounging: Post Invoice Reversal (Acctng Invoice Receipt)ACC_MAN_ALLOC01 Accounting: Post Manual Cost AllocationACC_PRIM_COSTS01 Accounting: Post primary costsACC_PRIM_COSTS02 Accounting: Post Primary CostsACC_PURCHASE_ORDER01 Accounting: Post Purchase OrderACC_PURCHASE_REQUI01 Accounting: Post Purchase RequisitionACC_REVENUES01 Accounting: Post revenuesACC_REVENUES02 Accounting: Post RevenuesACC_SALES_ORDER01 Accounting: Post Sales OrderACC_SALES_QUOTA01 Accounting: Post Customer QuotationACC_SENDER_ACTIVITIES01 Accounting: Post Sender ActivitiesACC_STAT_KEY_FIG01 Accounting: Post statistical key figuresACC_TRAVEL01 Accounting: Post tripACLPAY01 Posting in Accounting: Incoming InvoiceACLREC01 Posting in accounting: Billing documentACPJOU01 Posting in Accounting from Materials ManagementACTIV3 Units in KK3

ACTIV4 Units in KK4ACTIVITYTYPEGROUP_ADDNODE01 Object BUS1115 (Activity Type Group) - Method AddNodeACTIVITYTYPEGROUP_CREATE01 Object BUS1115 (Activity Type Group) - Method CreateADR2MAS01 BAPI for inbound distribution of private addressesADR2MAS02 BAPI for inbound distribution of private addressesADR3MAS01 BAPI for inbound distribution of contact person addressesADR3MAS02 BAPI for inbound distribution of contact person addressesADRMAS01 BAPI for inbound distribution of organizational addressesADRMAS02 BAPI for inbound distribution of organizational addressesALEAUD01 Confirmations of the processing status of inbound IDocsALEREQ01 General request - Basis IDoc typeARTMAS01 Create and Change Material Master Data (Retail)ARTMAS02 Create and Change Material Master Data (Retail)ARTMAS03 Create and Change Material Master Data (Retail)ARTMAS04 Create and change material master data (retail)ASSETACQUISITION_POST01 Post Asset AcquisitionASSET_POSTCAP_POST01 Post post-capitalizationASSET_RETIREMENT_POST01 Post asset retirementASSMOD01 Assortment (manual modules)ASSORTMENT01 Maintenance of assortmentsATT_ABS01 BAPI ext. Att./absence: Insert in IFT (w/o acct assgnmnt)ATT_ABS_WITH_ACTIVITY01 Ext. Att./absence (PTManagerExtAttAbs)ATT_ABS_WITH_COST01 BAPI ext. Att./absence: Insert in IFT (acct assgnmnt)BANK_CHANGE01 Change bankBANK_CREATE01 Create bankBANK_SAVEREPLICA01 Duplicate individual banks (ALE)BAPIPOHISTORYFROMDELIVERY01 Purchase Order, DeliveryBATCH5 Batch in CC5BATMAS01 Replicate batchBATMAS02 Replicate BatchBATMAS03 Replicate batchBBPCO01BBPIV01 BBP Create InvoiceBBP_IV_T01 EBP Create InvoiceBENEFIT1 HR: BenefitsBENEFIT2 HR: Benefits ParticipationBENEFIT3 HR: Benefits ParticipationBENEFITRET1 HR: Benefits Pension SchemesBETMAS01 Site master data distribution ALEBLAORD01 Purchasing contractsBLAORD02 Purchasing contractsBLAORD03 Purchasing contractsBLAREL01 Contract release order statisticsBLAREL02 Contract release order statistics

BMUMAS01 Replicate batch-specific material quantity unitsBOMDOC01 Master BOM - documentBOMDOC02 Master BOM - documentBOMMAT01 Master BOM - materialBOMMAT02 Master BOM - material (2)BOMMAT03 Material BOM (from 4.6B)BOMMAT04 Material BOM with UPS LinkBOMORD01 Master BOM - sales orderBTC_ID01 Process order with componentsBTC_ID02 Production requirement from superior systemBTC_ID03 Production commitment to superior systemBUPAFS_FS_CREATE_FRM_DATA01 SAP BP, BAPI: Create Business PartnerBUPA_C_ADDADDRESS01 SAP BP, BAPI: Add AddressBUPA_C_ADDIDENTIFICATION01 SAP BP, BAPI: Add Identification NumberBUPA_C_ADDSTATUS01 Business Partner: Add StatusBUPA_C_BANKDETAIL_ADD01 SAP BP, BAPI: Add Bank DetailsBUPA_C_BANKDETAIL_CH01 SAP BP, BAPI: Read Bank DetailsBUPA_C_BANKDETAIL_REMOVE01 SAP BP, BAPI: Delete Bank DetailsBUPA_C_CHANGEADDRESS01 SAP BP, BAPI: Change AddressBUPA_C_IDENTADD01 SAP BP, BAPI: Add Identification NumberBUPA_C_IDENT_REMOVE01 SAP BP, BAPI: Delete Identification NumbersBUPA_C_INDUSTRYSADD01 SAP BP, BAPI: Add IndustriesBUPA_C_INDUSTRYS_REMOVE01 SAP BP, BAPI: Delete Industry DataBUPA_C_PASSWORD_CH01 Change Password of Business Partner Internet UsersBUPA_C_PASSWORD_CR01 Create B2C Internet User for Business PartnerBUPA_C_PASSWORD_DELETE01 Delete a Business Partner Internet UserBUPA_C_PASSWORD_INIT01 Initialize Password for Business Partner Internet UserBUPA_C_REMOVEADDRESS01 SAP BP, BAPI: Delete AddressBUPA_C_ROLEADD01 SAP BP, BAPI: Add RoleBUPA_C_STATUS_REMOVE01 Business Partner: Delete StatusBUPA_C_TAXNUMBERADD01 BAPI Add Tax NumberBUPA_C_TAXNUM_CHANGE01 Change Tax NumberBUPA_C_TAXNUM_REMOVE01 Delete Tax NumberBUPA_FS_ADDADDITIONALDATA01 Add More Data to a Business PartnerBUPA_FS_ADDADDRESS01 Create Address (FS Business Partner)BUPA_FS_ADDADRESSUSAGE01 Create Address UsageBUPA_FS_ADDBANK01 BAPI for Adding Bank AttributesBUPA_FS_ADDCUSTOMFIELDS01 Create Employment Data for Business PartnerBUPA_FS_ADDDIFFTYPE01 Create Differentiation Type-Dependent AttributesBUPA_FS_ADDEMPLOYM01 ADD Bapi for Business Partner Employment DataBUPA_FS_ADDEXTERNID01 Create an External Identification NumberBUPA_FS_ADDFISCYEAR01 BAPI: Create Fiscal Year InformationBUPA_FS_ADDRATING01 Business Partner: RatingsBUPA_FS_ADDREPORTING01 Create Reporting Data for a Business PartnerBUPA_FS_ADDTREASURY01 Bapi to Create FS BuPa AttributesBUPA_FS_BANK_REMOVE01 REMOVE BAPI for Bank Data

BUPA_FS_CHANGE01 SAP BP, BAPI: Change Central DataBUPA_FS_CHANGEADDITIONALDATA01 Change Additional Data for a Business PartnerBUPA_FS_CHANGEADRESSUSAGE01 Change Address UsageBUPA_FS_CHANGEBANK01 Change in Bank RelationshipsBUPA_FS_CHANGECUSTOMFIELDS01 Change Employment Data for Business PartnerBUPA_FS_CHANGEDIFFTYPE01 Change Differentiation Type-Dependent AttributesBUPA_FS_CHANGEEMPLOYM01 CHANGE Bapi for Business Partner Employment DataBUPA_FS_CHANGEFISCYEAR01 BAPI: Change Fiscal Year InformationBUPA_FS_CHANGERATING01 Business Partner: Change RatingsBUPA_FS_CHANGEREPORTING01 Change Reporting Data for a Business PartnerBUPA_FS_CHANGETREASURY01 Change Business Partner Attribute (BusinessPartnerFS)BUPA_FS_CHGADDRESS01 Change Address (FS Business Partner)BUPA_FS_REMADDRESS01 Delete Address (FS Business Partner)BUPA_FS_REMOVEADDITIONALDATA01 Delete Additional Data for a Business PartnerBUPA_FS_REMOVEADRESSUSAGE01 Delete Address UsageBUPA_FS_REMOVECUSTOMFIELDS01 Delete Employment Data for Business PartnerBUPA_FS_REMOVEDIFFTYPE01 Delete Differentiation Type-Dependent AttributesBUPA_FS_REMOVEEMPLOYM01 CHANGE Bapi for Business Partner Employment DataBUPA_FS_REMOVEEXTERNID01 Delete an External Identification NumberBUPA_FS_REMOVEFISCYEAR01 BAPI: Delete Fiscal Year InformationBUPA_FS_REMOVERATING01 Business Partner: Delete RatingsBUPA_FS_REMOVEREPORTING01 Delete Reporting Data for a Business PartnerBUPA_FS_REMOVETREASURY01 Delete Business Partner Attribute (BusinessPartnerFS)BUS1151_CREATE01 Create Architectural ObjectBUS1501_CREATE01 Create Business EntityBUS1502_CREATE01 Create propertyBUS1503_CREATE01 Create buildingBUS1504_CREATE01 Create Rental ObjectBUS1505_CREATE01 Create Real Estate ContractBUSINESSPARTNERFS_FSADDROLE01 SAP BP, BAPI: Create Business PartnerBUSINESSPROCESSCOGRP_ADDNODE01 Object BUS1114 (Business Process Group) - Method AddNodeBUSINESSPROCESSCOGRP_CREATE01 Object BUS1114 (Business Process Group) - Method CreateCACS00 Commission Case Application CACS00CAP_ACTIN01 Activity input planning: PostingCAP_ACTIN02 Activity Input Planning: PostingCAP_ACTOUT01 Activity/Price planning: Posting

CAP_ACTOUT02 Activity/Price Planning: PostingCAP_KEYFIG01 Stat. Key Figure Planning: PostingsCAP_PRIMCOST01 Primary Cost Planning: PostingsCATS_CHANGE01 CATS: Change data recordsCATS_CHANGE02 CATS: Change data recordsCATS_DELETE01 CATS: Delete data recordsCATS_INSERT01 CATS: Insert data recordsCATS_INSERT02 CATS: Insert data recordsCBPRCP01 Rough-cut planning profileCCLONE01 Duplicate company address in another systemCHARACTERISTIC_CREATE01 BAPI for Characteristics - CreateCHRMAS01 Master characteristic basic dataCHRMAS02 Master attribute with object dependenciesCHRMAS03 Distribute Characteristics with Dependencies and Long TextsCHRMAS04 Distr. of Characteristics with Dependencies and Long TextsCLASSIFICATION_CREATE01 BAPI for Classification: Create Assignment (Key)CLASS_CREATE01 Create Class BAPICLASS_CREATESUBCLASSALLOCATI01 Class Hierarchy BAPI: Create AssignmentCLASS_CREATESUBSTRUCTURE01 Class Hierarchy BAPI: Create Hierarchy (Top Down)CLFMAS01 Master object classificationCLFMAS02 Master object classificationCLSMAS01 Master classCLSMAS02 Distribution of classes with object dependenciesCLSMAS03 Classes with long texts and document linksCLSMAS04 Classes with Long Texts, Document Links, and E1UPSLINKCMREQU01 TR-CM: Invitation to TR-CM system to send dataCMSEND01 TR/CM-IDOC: Transfer of TR-CM dataCNPMAS01 Master configuration profileCNPMAS02 Master configuration profileCNPMAS03 Master Configuration Profile + E1UPSLINKCOABCM01 Replicate individual business process (ALE)COABCV01 ALE: replicate price from business processesCOABC_BUSPROCSTRUCTURE_CREAT01 Create process struct.(BusProcStructureCO)COACOR01 Core master activity typeCOACTV01 IDoc for cost center/activity typeCOAMAS01 Master activity typeCOCOKA01 Control segment CO object/cost elementCODCMT01 IDoc for a CO documentCOELEM01 Cost elements: Master data distributionCOGRP01 IDoc for CO groups (e.g. cost center groups)COMM_ITEM01 Commitment Item MasterCONDA201 ALE Customizing Distribution Add-OnCONDAT01 Change to customizing dataCONDAT02 Distribution of Control Data

COND_A01 Interchange of conditions: Master data for price determ.COND_A02 ALE condition recordsCOND_A03 Conditions with UPS LinkCONF11 Confirmations in CC1CONF21 Confirmations in KK2, time eventsCONF31 Confirmations in KK3, time eventsCONF32 Confirmations in KK3, wage slipsCONF41 Confirmations in KK4, time eventsCONF42 Confirmations in KK4, wage slipsCONF51 CC5 PDC Interface KANBANCONF_ACT1001 Enter activity confirmationCOPAGN01 CO-PA entryCOPA_DERIVE_ADD_VALUES01 Derivation Rule: AddValuesCOPA_DERIVE_REMOVE01 Derivation Rule: RemoveValuesCOPA_WW_ADD_VALUES01 Individual Characteristic: AddValuesCOPA_WW_GET_VALUES01 Characteristic: GetValuesCOPA_WW_REMOVE_VALUES01 Individual Characteristic: RemoveValuesCOPCPA01 Transfer product costing CO-PC -> CO-PACOPCPA02 Copy product cost estimateCOSCOR01 Core master cost centerCOSMAS01 Master cost centerCOSTCENTERGROUP_ADDNODE01 Object BUS1112 (Cost Center Group) - Method AddNodeCOSTCENTERGROUP_CREATE01 Object BUS1112 (Cost Center Group) - Method CreateCOSTELEMENTGROUP_ADDNODE01 Object BUS1113 (Cost Element Group) - Method AddNodeCOSTELEMENTGROUP_CREATE01 Object BUS1113 (Cost Element Group) - Method CreateCOTOTL01 IDoc for CO totals recordsCO_ABC_BPROC_CREATE01 Create one or more business processesCO_ABC_BPROC_SETSTRUC01 Enter template in business process master dataCRECOR01 Vendor master data distribution ALE Core master dataCREMAS01 Vendor master data distribution ALECREMAS02 Vendor master data distribution ALECREMAS03 Vendor master data distributionCREMAS04 Vendor master data distributionCREMDM01 MDM: Mass Processing CREMAS (Vendor Master)CREMDM02 MDM: Mass Processing CREMAS (Vendor Master + Addresses)CREMDM03 MDM: Mass Processing CREMAS (Vendor Master + Addresses)CREMDM04 MDM: Mass Processing CREMAS (Vendor Master + Addresses)CRESTA01 Copy credit status (DebtorCreditAccount)CUSTOMERRETURN_CONFIRMDELIVE01 Delivery Confirmation (CustomerReturn)CUSTSCHEDULAGREEMENT_CONFDEL01 Delivery Confirm. (CustSchedulAgreement)

CUSTSCHEDULAGREEMENT_CONFIRM01 Delivery Confirmation (CustSchedulAgreement)DANGEROUSGOOD01 Dangerous goods: Save replicated instancesDANGEROUSGOOD02 Dangerous goods: Save replicated instancesDD01L_01 DomainsDD03L_01 Table FieldsDD04L_01 Data elementsDEBCOR01 Core master - customerDEBMAS01 Customer masterDEBMAS02 Customer masterDEBMAS03 Customer masterDEBMAS04 Customer master data distributionDEBMAS05 Customer Master Data DistributionDEBMAS06 Customer master data distributionDEBMDM01 MDM: Mass-enabled DEBMAS (Customer Master)DEBMDM02 MDM: Mass-enabled DEBMAS (Customer Master)DEBMDM03 MDM: Mass Processing DEBMAS (Customer Master + Addresses)DEBMDM04 MDM: Mass Processing DEBMAS (Customer Master + Addresses)DEBMDM05 MDM: Mass Processing DEBMAS (Customer Master + Addresses)DEBMDM06 MDM: Mass Processing DEBMAS (Customer Master + Addresses)DELFOR01 Delivery schedule/JIT scheduleDELFOR02 Delivery Schedule/JIT ScheduleDELIVERYPROCESSING_EXECUTE01 Delivery processingDELVRY01 Delivery interfaceDELVRY02 Delivery interface with dangerous goods dataDELVRY03 Delivery interfaceDEPNET Master data of dependency netDEPNET02 Master Data of a Dependency Net + E1UPSLINKDESADV01 External service agent processing (notifications)DES_ID01 Shipping notificationDIFFE2 Differences in KK2DIFFE3 Differences in KK3DIFFE4 Differences in KK4DISPUTE_ATTRIBUTESCHANGE01 FSCM-DM: Change Dispute Case AttributesDISPUTE_CREATE01 FSCM-DM: Creation of Dispute CaseDISPUTE_PROCESS01 FSCM-DM: Process Dispute CaseDISPUTE_STATUSCHANGED01 FSCM-DM: Change Status of Dispute CaseDISPUTE_WRITEOFF01 FSCM-DM: Dispute Cases to be Written Off AutomaticallyDISTU2 Reasons for problems KK2DOCMAS01 Master documentDOCMAS02 Document 02DOCMAS03 DocumentDOCMAS04 DocumentsDOCMAS05 Documents with UPS LinkDOCUMENT_LOAD01 Load document data (Document transfer)DOLMAS01 Document-object links

DOLMAS02 Document-Object Links with UPS LinkDSPMAS01 ALE Distribution PacketDSPRCP01 ALE Distribution PacketDWLOAD Download transceiver configurationDXPROJECT_CREATE01 Create Method of Business Object DXPROJECTDXPROJECT_CREATE02 Create Method of Business Object DXPROJECTDXPROJECT_CREATE03 Create Method of Business Object DXPROJECTDXTCRE01 Object SBFADXTECMMAS01 IDoc structure for ECHECMMAS02 Change number (II)ECMREV01 IDOC structure for revision levelEEWAGECOMP_CHANGE01 Modification of External Wage ComponentEEWAGECOMP_CREATE01 Creation of Infotype Record for External Wage ComponentEEWAGECOMP_DELETE01 Deletion of External Wage ComponentEHPOST01 SCEM: Event Handler PostingEKSEKS01 Purchasing document data for Purchasing Info SystemEMPWAGECOMPEXT_CHANGE01 Modification of External Wage ComponentEMPWAGECOMPEXT_CREATE01 Creation of External Wage ComponentEMPWAGECOMPEXT_DELETE01 Deletion of External Wage ComponentEQUIPMENT_CHANGE01 PM BAPI: Change EquipmentEQUIPMENT_CREATE01 PM BAPI: Create EquipmentEVMSTA01 SCEM: Event Message InputEVMSTA02 SCEM: Event Message InputEXCHANGE_RATE01 Replication of Currency RatesEXPINV01 Export Invoice IDOC (E.F.I.)EXPINV02 Foreign Trade - Billing Doc. IDocEXPINV03 Foreign trade - billing doc. IDocEXPINV04 Foreign trade - billing doc. IDocEXTSECURITYACCSTMNT_CREATE01 Create External Security Account StatementEXTWA1 External wage typesFIDCCH01 IDoc for FI document changes (dunning block)FIDCCP01 IDoc: Complete FI documentFIDCCP02 FI IDoc: Complete FI DocumentFIDCMT01 IDoc for FI documentsFINANCIALPRODUCT_CREATE01 Create securityFINANCIALTRANSACTION_CREATE01 Create financial transactionFINSTA01 Account Statement, Lockbox, Polling InfoFIPARQ01 IDoc for FI payment dataFIXEDASSET_CHANGE01 Changes an assetFIXEDASSET_CHANGE02 Changes an assetFIXEDASSET_CHANGE03 Changes an AssetFIXEDASSET_CREATE01 Creates an assetFIXEDASSET_CREATE02 Creates an assetFIXEDASSET_CREATEFROMDATA101 Creates an AssetFIXEDASSET_CREATEFROMDATA102 Creates an Asset

FIXEDASSET_CREATEINCLVALUES01 BAPI for Legacy Data TransferFIXEDASSET_CREATEINCLVALUES02 BAPI for Legacy Data TransferFLCUSTOMER_CREATEFROMDATA01 Create new customerFLIGHTBOOKING_CANCEL01 Cancel flight bookingFLIGHTBOOKING_CONFIRM01 Confirm flight bookingFLIGHTBOOKING_CREATEFROMDAT01 Create flight bookingFLIGHTCUSTOMER_CHANGE01 Change Flight CustomerFLIGHT_SAVEREPLICA01 Save replicated flight dataFTDABA01 Foreign Trade Data Service Basic DataFTDACU01 Foreign Trade Data Service Customs DataFTRCON01 Confirm transactionFTRPAYMENTDETAIL_GETLIST01 List of Payment DetailsFTR_ADDFLOW_CHANGE01 FTR: RFC for Method 'Paymentdetail.Create'FTR_ADDFLOW_CREATE01 FTR: RFC for Method 'Paymentdetail.Create'FTR_ADDFLOW_DELETE01 FTR: RFC for Method 'Paymentdetail.Delete'FTR_ADDFLOW_GETLIST01 FTR: RFC for Method 'Paymentdetail.Create'FTR_CFT_CHANGE01 Change Cash Flow-Dependent TransactionFTR_CFT_CREATE01 Create Cash Flow-Dependent TransactionFTR_CFT_FLOWCHANGE01 FTR: RFC for Method 'Paymentdetail.Create'FTR_CFT_FLOWCREATE01 FTR: RFC for Method 'Paymentdetail.Create'FTR_CFT_FLOWDELETE01 FTR: RFC for Method 'Paymentdetail.Delete'FTR_CFT_FLOWGETLIST01 FTR: RFC for Method 'CFT.CashflowGetList'FTR_CFT_GETDETAIL01 Details of a cash flow-dependent transactionFTR_CFT_REVERSE01 Reverse Cash Flow-Dependent TransactionFTR_CONDITION_CHANGE01 RFC for Method Condition.ChangeFTR_CONDITION_CREATE01 RFC for Method Condition.CreateFTR_CONDITION_DELETE01 RFC for Method Condition.DeleteFTR_CONDITION_GETLIST01 RFC for Method Condition.GetListFTR_COUNTERCONFIRM01 Counterconfirm financial transactionFTR_CP_CHANGE01 Change Commercial PaperFTR_CP_CREATE01 Create Commercial PaperFTR_CP_GETDETAIL01 Details of a fixed-term depositFTR_CP_REVERSE01 Reverse Fixed-Term Deposit per BAPIFTR_DAN_CHANGE01 Change fixed-term deposit per BAPIFTR_DAN_CREATE01 Create fixed-term depositFTR_DAN_GETDETAIL01 Details of a fixed-term depositFTR_DAN_GIVENOTICE01 Roll Over Fixed-Term Deposit per BAPIFTR_DAN_MAINFLOWCHANGE01 FTR: RFC for Method 'FinancialTransaction.MainFlowCreate'FTR_DAN_MAINFLOWCREATE01 FTR: RFC for Method 'Paymentdetail.Create'FTR_DAN_MAINFLOWDELETE01 FTR: RFC for Method 'Paymentdetail.Delete'FTR_DAN_MAINFLOWGETLIST01 FTR: RFC for Method 'Paymentdetail.Create'FTR_DAN_REVERSE01 Reverse Fixed-Term Deposit per BAPIFTR_DAN_ROLLOVER01 Roll Over Fixed-Term Deposit per BAPIFTR_FTD_CHANGE01 Change fixed-term deposit per BAPIFTR_FTD_CREATE01 Create fixed-term deposit

FTR_FTD_GETDETAIL01 Details of a fixed-term depositFTR_FTD_MAINFLOWCHANGE01 FTR: RFC for Method 'FinancialTransaction.MainFlowCreate'FTR_FTD_MAINFLOWCREATE01 FTR: RFC for Method 'Paymentdetail.Create'FTR_FTD_MAINFLOWDELETE01 FTR: RFC for Method 'Paymentdetail.Delete'FTR_FTD_MAINFLOWGETLIST01 FTR: RFC for Method 'Paymentdetail.Create'FTR_FTD_REVERSE01 Reverse Fixed-Term Deposit per BAPIFTR_FTD_ROLLOVER01 Roll Over Fixed-Term Deposit per BAPIFTR_FXOPTION_CHANGE01 Change an FX OptionFTR_FXOPTION_CREATE01 Create Currency OptionFTR_FXOPTION_EXERCISE01 Exercise FX OptionFTR_FXOPTION_EXPIRE01 Allow FX Option to ExpireFTR_FXOPTION_GETDETAIL01 Details on FX OptionsFTR_FXOPTION_KNOCKIN01 Knockin FXOPTIONFTR_FXOPTION_KNOCKOUT01 Knockout FXOPTIONSFTR_FXOPTION_REVERSE01 Reverse FX OptionFTR_FXOPTION_SETTLE01 Cancel FX OPTIONFTR_FXT_CHANGE01 Change forex transactionFTR_FXT_CREATE01 Create forex transactionFTR_FXT_GETDETAIL01 Details of a forex transactionFTR_FXT_REVERSE01 Reverse forex transactionFTR_FXT_SETTLE01 Settle Forex TransactionFTR_FX_CREATESWAP01 Create Forex TransactionFTR_FX_CREATESWAP011 Create Currency SwapFTR_GETDETAIL01 Read transaction detailed dataFTR_GETLIST01 Read transaction listFTR_IRATE_CHANGE01 Change interest rate instrumentFTR_IRATE_CREATE01 Create interest rate instrumentFTR_IRATE_GETDETAIL01 Create interest rate instrumentFTR_IRATE_MAINFLOWCHANGE01 FTR: RFC for Method 'FinancialTransaction.MainFlowCreate'FTR_IRATE_MAINFLOWCREATE01 FTR: RFC for Method 'Paymentdetail.Create'FTR_IRATE_MAINFLOWDELETE01 FTR: RFC for Method 'Paymentdetail.Delete'FTR_IRATE_MAINFLOWGETLIST01 FTR: RFC for Method 'Paymentdetail.Create'FTR_IRATE_REVERSE01 Reverse interest rate instrumentFTR_PAYDET_CHANGE01 FTR: RFC for Method 'Paymentdetail.Create'FTR_PAYDET_CREATE01 Create Payment DetailsFTR_PAYDET_DELETE01 FTR: RFC for Method 'Paymentdetail.Delete'FTR_PAYDET_GETLIST01 FTR: RFC for Method 'Paymentdetail.Create'FTR_SECURITY_CHANGE01 Change security transactionFTR_SECURITY_CREATE01 Create security transactionFTR_SECURITY_GETDETAIL01 Security transaction detailsFTR_SECURITY_REVERSE01 Reverse Security TransactionFTR_SECURITY_SETTLE01 Settle Security TransactionFTR_SETTLE01 Settle financial transactionFUNC_LOC_CHANGE01 PM BAPI: Change Functional Location

FUNC_LOC_CREATE01 PM BAPI: Create Functional LocationFUNDMA01 IDoc: Funds Management FundFUNDSCTR FundsManagement: Funds CenterGLCORE01 Documentation deletedGLDCMT01 IDoc type for GLX rollupsGLMAST01 Master data G/L accounts: Max. IDocGOODSMVT_SAPCREATE01 SAP Internal Cross-System Flow of GoodsGSVERF01 IDoc input credit memo procedureGSVERF02 Cred. memo procedureGSVERF03 Cred. memo procedureHRCC1DNATTAB01 CC1: Download permitted att./absence reasonsHRCC1DNBALAN01 CC1: Download Employee BalancesHRCC1DNCOSTC01 CC1: Download Cost CentersHRCC1DNEXTWT01 CC1: Download permitted external wage typesHRCC1DNINORD01 CC1: Download Internal OrdersHRCC1DNOBJID01 CC1: Download Objects (such as Positions)HRCC1DNPERSO01 CC1: Download HR Mini-MasterHRCC1DNTEVGR01 CC1: Download Time Event Type GroupsHRCC1DNWBSEL01 CC1: Download Work Breakdown Structure ElementHRCC1REQUPEXTWT01 CC1: Upload Request for Employee ExpendituresHRCC1REQUPTEVEN01 CC1: Upload Request for Time EventsHRCC1UPEXTWT01 CC1: Upload external wage typesHRCC1UPTEVEN01 CC1: Upload time eventsHRCNF01 Transfer confirmations (TimeMgtConfirmation)HRKK1ABSR HR TIM CC1: Allowed Attedance/Absence ReasonsHRKK1EWUP HR TIM CC1: External Wage Types ConfirmationHRKK1EXWT HR TIM CC1: Permitted External Wage TypesHRKK1PERS HR TIM KK1: HR Mini Master for Time RecordingHRKK1TBAL HR TIM CC1: Employee Time BalancesHRKK1TEUP HR TIM KK1: Confirmation of person time eventsHRKK1TEVT HR TIM CC1: Permitted Time Event TypesHRKK1WRKC HR TIM CC1: Permitted Work CentersHRMASTER01 Replicate (HRMasterDataReplica)HRMASTER02 Replicate (HRMasterDataReplica)HRMD_A01 HR: Master and organizational data (application system)HRMD_A02 HR: Master and organizational data (application system)HRMD_A03 HR: Master and organizational data (application system)HRMD_A04 HR: Master and organizational data (application system)HRMD_A05 HR: Planning and HR Master Data (Application System)HRMD_A06 HR: Planning and HR Master Data (Application System)HRMD_ABA01 HR: Master & Organizational Data (Application Basis System)HRMD_ABA02 HR: Master and Plan Data (Application Basis System)HRMD_ABA03 HR: Plan & Personnel Master Data (Application Basis System)HRMD_ABA04 HR: Plan & Personnel Master Data (Application Basis System)HRMD_B01 HR: Master and organizational data (basis system)HRMD_B02 HR: Master and organizational data (basis system)

HRMD_B03 HR: Master and Planning Data (Basis System)HRMD_B04 HR: Master and Planning Data (Basis System)HROT558D HR: Outsourcing US: Inbound IDOC Table T558A (Test)HROTIN HR: Outsourcing: Inbound Payroll ResultsHROTUSTR HR-PY-US : Tax Remittance OutsourcingHROT_BRM HR: BR Master data payroll outsourcingHROT_CAM HR: Canadian Master Data Payroll OutsourcingHROT_CAP Payroll Outsourcing - CanadaHROT_CHM HR: CH Master data payroll outsourcingHROT_DEM HR: DE Master data payroll outsourcingHROT_ESM HR: ES Master data payroll outsourcingHROT_FIM HR: FI Master Data Payroll Export - OutsourcingHROT_FRM HR: FR Master data payroll outsourcingHROT_GBM HR: GB Master data payroll outsourcingHROT_IEM HR: IE Master data payroll outsourcingHROT_ITM HR: IT Master data payroll outsourcingHROT_NLM Master Data Outsourcing - The NetherlandsHROT_NLP Gross payroll outsourcing - The NetherlandsHROT_TM HR: Outsourcing Time Wage TypesHROT_USM HR: US Master Data Payroll OutsourcingHROT_USP HR: Generic US Payroll OutsourcingHROT_USTP Outsourcing: US Tax Services - PeriodicHROT_USTQ Outsourcing: US Tax Services - QuarterlyHROT_USTY Outsourcing: US Tax Services - Yearly ReportingHROT_XXM HR: International Master Data Payroll OutsourcingHROT_XXP HR: Generic International Payroll OutsourcingHRPAYP01 HR - Transfer FI/COHRPLL40 Logistics confirmations for Human Resource ManagementHRSM_A01 HR: HR data for personnel actionsHRSM_A03 HR: HR data for personnel actionsHRSM_B01 HR: Confirmation for personnel actionsHRSM_C01 HR: Download TIme DataHRSM_D01 HR: Time Data UploadHRTRPR01 Transfer TRV-PAY(PayrollTravelExpenses)HRTRVL01 HR-TRV: Transfer travel expenses FI/COHRTRVL03 HR-TRV: Transfer Trip Costs to PayrollHR_INBND HR: OUTSOURCING: Inbound IDoc TablesHU_CREATE01 Create handling unit with itemsHU_DELETE01 BAPI for deleting handling unitsHU_PACK01 BAPI for packing an item into an HUHU_PROCESSOUTPUTDIRECT01 Select and process handling-unit outputsHU_REPACK01 Repack HUs and HU itemsHU_UNPACK01 BAPI for unpacking an item from an HUIDCREF01 Reference message as logical grouping for electron.signatureIMATIS01 Unplanned material issuesIMEASR01 Measurement reading IDOC

IMPINV01 Import Basis IDoc (I.B.I.)IM_PROGDEF_SAVEREPLICA01 Method 'SaveReplica' for ExpenditureProgDefINFREC01 Purchasing info recordINFRECMASS01 Purchasing Info Records (Mass IDOC)INOTIF01 Notification IDOCINSPECTIONPLAN_CREATE01 Create Inspection PlanINTERNALORDERGROUP_ADDNODE01 Object BUS1117 (Order Group) - Method AddNodeINTERNALORDERGROUP_CREATE01 Object BUS1117 (Order Group) - Method CreateINTERNAL_ORDER01 Replicate individual internal order (ALE)INTERNAL_ORDER_CREATE01 Create internal order from transferred dataINTERNAL_ORDER_CREATE02 Create Internal Order From Transferred DataINTUPD01 Notification status update IDocINVCON01 Stock change data for inventory controllingINVOIC01 Invoice/Billing documentINVOIC02 Invoice/Billing documentINV_ID01 InvoiceIOAUPD01 Work order assignments IDOCIORDER01 SM/PM order IDocIORUPD01 Order status update IDocIWKCEN01 Work Center IDOCJOBROLE_CLONE01 Create a user (job role)JV_EXP01 Joint Venture Billing - Operating Exp StatementJV_EXP02 Joint Venture Billing - Operating Expenditure StatementJV_INV01 Joint Venture Billing - InvoiceKANBAN01 Kanban Call for Kanban With SD DeliveryKNOMAS01 Master Dependency Basic DataKNOMAS02 Master Dependency Basic DataLABELS00 ISR labeling: labelLAYMOD01 Distribution of Layout ModulesLIKOND01 Listing conditionsLIS_EXTR LIS inbound interface for external dataLOCAT5 Location in KK5LOIBOM01 Master bill of materialLOICAL01 Master calendarLOIMSO01 Storage location stock materialLOINUM01 Number of IDocs sentLOIPGR01 IDOC for product groupLOIPLO01 Master planned orderLOIPRO01 Master production orderLOIRNH01 Master hierarchy/networksLOIROU01 Master routingLOIROU02 Master routingLOIRSH01 Master run schedule headerLOISTD01 Master requirements/stock list

LOITMX01 Transition matrixLOIWCS01 Master work centerLOIWCS02 Master work center IDocLPIEQU01 IDoc: quota arrangementLPIPCM01 Production campaignMALFK5 CC5 reasons for scrapMANAGEREXTPAYROLL_INSERTLEGA01 Transfer payroll accountMANAGEREXTPAYROLL_INSERTOUT01 Update of a payroll result using an outsourcerMATCOR01 Core master materialMATERIALBOM_CREATEBOMGROUP01 Creation of a material BOM groupMATERIALPHYSINV_COUNT01 Enter Inventory Count (MaterialPhysInv)MATERIALPHYSINV_CREATEMULTIP01 Create physical inventory documentMATERIALPHYSINV_POSTDIFFEREN01 Post Differences (MaterialPhysInv)MATERIALRESERVATION_CREATE101 BAPI to Create Individual ReservationsMATERIALRESERVATION_DELETE01 BAPI to Delete Individual ReservationsMATERIALVALUATION_PRICECHANG01 Material Price ChangeMATMAS01 Material MasterMATMAS02 Material MasterMATMAS03 Material MasterMATMAS04 Material MasterMATMAS05 Enhancement: Distribution of Single-Level VariantsMATMAS_BAPI01 Create and Change Material Master DataMATMAS_MASS_BAPI01 BAPI for Mass Maintenance of Material DataMATQM01 Replication of QM Inspection SetupMATTYPE01 Material TypesMBGMCA01 Reverse goods movements with MB_CANCEL_GOODS_MOVEMENTMBGMCR01 BAPI Posting of goods mvts with MB_CREATE_GOODS_MOVEMENTMBGMCR02 Post goods movements with MB_CREATE_GOODS_MOVEMENTMC1_01 Condition tablesMDMFDB01 MDM: Feedback Idoc (Object status)MDMMETA MDM MetadataMDMRECEIPT01 MDM ReceiptMDMREQUEST01 MDM RequestMDMVERA MDM Verification SFLIGHTMDM_EQUIPMENT_SAVEREPLICA01 BAPI for Mass Maintenance of EquipmentMDM_FUNCLOC_SAVEREPLICA01MMADDI01 Create and change additionals (retail)MRESCR01 Create reservationOBDLV_PROCOUTP01 Process delivery output without listOPERA2 Operations in KK2OPERA3 Processes in KK3OPERA4 Operations in KK4OPERS3 Operation status in KK3OPERS4 Operation status in KK4ORDERS01 Purchasing/Sales

ORDERS02 Purchasing/SalesORDERS03 Purchasing/SalesORDERS04 Purchasing/SalesORDERS05 Purchasing/SalesORD_ID01 Req.for quot./quotation/purchase order/order changeORGMASTER01 BAPI for replication of HR organizational dataOSTAT2 Process status CC2PALMAT01 Plant assignment to material BOMPAYMENTREQUEST_CANCEL01 Cancelation of a Payment RequestPAYMENTREQUEST_CREATE01 Creation of a Payment RequestPAYMENTREQUEST_POST01 Posting a Parked Payment RequestPAYMENTREQUEST_RELEASE01 Payment Request Released for PaymentPAYMENTREQUEST_STARTPAYMENT01 Start Payment of Payment RequestPCHEAD01 Replicate basic and structure data of a product catalogPCITEMS01 Replicate item data of a product catalogPDTCO_POSTPRIMARY01 Transfer of Planning Data: Post Primary CostsPEROP2PERSO1 Personnel master records in CC1PERSO2 Personnel master in CC2PERSO3 Personnel master in CC3PERSO4 Personnel master in CC4PEXR2001 Payment/payment advice note/credit memo/debit advicePEXR2002 Payment/payment advice note/credit memo/debit advicePHRMAS01 EHS: Saving Replicated PhrasesPIECEOFEQUIPMENT_DISMANTLEAT01 Dismantle equipment at functional locationPIECEOFEQUIPMENT_INSTALLATFU01 Install equipment at functional locationPKHD5 CC5 kanban control cyclesPKPS5 CC5 Kanban containerPKST5 CC5 status for kanban containerPLANDATATRANSFERCO_POSTACTIO01 Planning Data Transfer: Post Activity PlanningPLANDATATRANSFERCO_POSTACTIV01 Planning Data Transfer: Post Activity InputPLANDATATRANSFERCO_POSTKEYFI01 Transfer of Planning Data: Post Stat. Key FiguresPLANT3 Plants in CC3PLANT4 Plants in CC4PORDCH01 Change purchase orderPORDCR01 Create purchase orderPORDCR02 Create purchase orderPORDCR03 Create purchase orderPORDCR04 Create purchase orderPORDCR05 Create Purchase OrderPORDCR101 Create Purchase OrderPORDGD01 Display Purchase Order Details

PO_DELETEPOHISTORY01 Delete Purchase Order HistoryPO_UPDATEPOHISTORY01 Update Purchase Order (Update, Insert)PPCC2PRETEVENT01 Transfer time event confirmations from PDC systemPPCC2PRETTICKET01 Transfer time ticket confirmations from PDC systemPPCC2RECORDER01 Send production orders to PDC systemPPCC2RECWORKCENTER01 Send work centers to PDC systemPPCC2REQCONF01 Send upload request to PDC systemPPE_ACT01 Maintain or Create Process StructurePPE_BAL01 Maintain or Create Line BalancesPPE_CMP01 Maintain or Create Product StructurePPE_FLO01 Maintain or Create Factory LayoutPPE_GEN01 Create and Change Generic Engineering NodePPE_PRM01 Create or Change iPEE Production ModelPPE_RES01 Maintain or Create iPPE Object Resources NodesPRCDOC01 Replicate PCA line items (ALE)PRCDOCD01 Delete profit center documents (ALE)PRCDOCP01 Replicate EC-PCA plan line items (ALE)PRCDOCR01 Reversal of existing document line items (ALE)PRCMAS01 Profit center master recordPRCMAS02 Profit Center master record (with company code assignment)PRDCAT01 Product catalogPRDPOS01 Product catalog itemPREQCR01 Create purchase requisitionPREQCR02 Create purchase requisitionPREQCR03 Create Purchase RequisitionPREQDL01 Delete/close purchase requisitionPRICAT01 Price/sales catalogPRICAT02 Price List/Sales CatalogPRICECATALOGUE01 Store price catalog instancePRICECATALOGUE02 Save Price Catalog InstancePROACT01 Transfer of stock and sales dataPROFITCENTERGROUP_ADDNODE01 Object BUS1116 (Profit Center Group) - Method AddNodePROFITCENTERGROUP_CREATE01 Object BUS1116 (Profit Center Group) - Method CreatePROFITCENTER_CHANGE01 Change Profit CenterPROFITCENTER_CREATE01 Create Profit CenterPROJECT01 Replicate entire work breakdown structure (ALE)PROMOTION_CONFIRMREQUEST01 Send Reply for Plant's Required QuantitiesPTOVERVIEW01 Insert/Delete employee time overviewsQALITY01 Quality data and sending of certificate referenceQALITY02 QM: Quality CertificateQPGR01 Replication of QM Code Groups/CatalogsQPMK01 Replication of QM Master Inspection (ALE)QSMT01 Replication of QM inspection methodsRCYINF01 Information about IDocs and their application documents

RCYSYS01 Information about the reset systemREDEMPTIONFACTORS_CHANGE01 BAPI: Create or Change a Redemption FactorREDEMPTIONFACTORS_CREATE01 BAPI: Create Redemption Factor Header + FactorsREDEMPTIONFACTORS_GETDETAIL01 BAPI: Read Redemption Factors for a Securities IDREDEMPTIONSCHEDSET_ADDSCHEDU01 Create Redemption Schedules for Redemption Schedule SetsREDEMPTIONSCHEDSET_CREATE01 Create Redemption Schedule SetsREDEMPTIONSCHEDSET_GETDETAIL01 Read Redemption Schedules for Redemption Schedule SetsREDEMPTIONSCHEDSET_GETLIST01 Read Header Data for Redemption Schedule SetsREDEMPTIONSET_CHANGESCHEDULE01 Change Repayment Schedule DataREFSETOFOPERATIONS_CREATE01 Creation of a reference operation setREMUNREQUESTLIST_GETLIST01 Determine Documents (RemunRequestList)REMURQSLIST_CHANGE01 Agency Business: Change Invoice List Documents BAPIREMURQSLIST_CREATE_CBD01 Create from posting list (invoice list)REMURQSLIST_CREATE_CBD02 Create from posting list (invoice list)REMURQSLIST_CREATE_REMU01 Create from shipping document (invoice list)REMURQSLIST_CREATE_REMU02 Create from shipping document (invoice list)REMURQSLIST_CREATE_SETT01 Create from payment document (invoice list)REMURQSLIST_CREATE_SETT02 Create from payment document (invoice list)REMURQSLIST_RELEASE01 Release to Accounting (Invoice List)REMURQSLIST_RELEASE02 Release to Accounting (Invoice List)REM_SPEC01 Insert Ext. EE Remun. Info in Table (w/o Account Assignment)REM_SPEC_WITH_ACTIVITY01 Insert employee remuneration info (PTMgrExtRemunSpec)REM_SPEC_WITH_COST01 Insert External EE Remun. Info in Table (w/ Cost Assignment)REPMAS01 EHS: Saving Replicated ReportsREQUI1 Confirmation request in CC1REQUI2 Confirmation request in CC2REQUI3 Confirmation request in CC2REQUI4 Confirmation request in CC4REQUI5 Confirmation request in CC5RESOURCECO01 Replicate Individual CO Resources (ALE)ROUTING_CREATE01 Creation of a routingRPLMAS01 Create and change replenishment master dataRPLMAS02 Create and Change Replenishment Master DataRPMINTF1 RPM FI InterfaceRSINFO Info IDocRSREQUST Data request to the source systemRSSEND Data transfer from the source system (template)SALESORDER_CONFIRMDELIVERY01 Delivery Confirmation (SalesOrder)SALESORDER_CREATEFROMDAT201 Sales order: Create Sales Order

SALESORDER_CREATEFROMDAT202 Sales order: Create Sales OrderSAPRDI01 SAPscript Raw Data Interface IDOC TypeSAPRDI02 SAPscript Raw Data Interface IDOC TypeSCERTKB Knowledge base for configuratorSDPAID01 Shipping element data confirmation to customer deliverySDPIID01 Picking data confirmation to customer deliverySDPIOD01 Picking notification to subsystem:SERDAT01 Control data serializationSERVICENOTIFICATION_CREATEFR01 Create service notificationSETTLEMENTREQUSTLIST_GETLIST01 Determine Documents (SettlementRequstList)SETTRQSLIST_CHANGE01 Agency Business: Change Settlement Request List BAPISETTRQSLIST_CHANGE02 Agency Business: Change Settlement Request List BAPISETTRQSLIST_CLOSE01 Agency Business: BAP(SettlementRequstList)SETTRQSLIST_CREATE01 Agency Business: Create Settlement Request List BAPISETTRQSLIST_CREATE02 Agency Business: Create Settlement Request List BAPISETTRQSLIST_RELEASE01 Release to Accounting (SettlementRequstList)SETTRQSLIST_RELEASE02 Release to Accounting (SettlementRequstList)SFADCH01 SFA download salesorder (change pointers)SFADDE01 SFA Download DebitorSFADOR01 SFA Download SalesorderSFADPSA01 BAPI Partner Sales Activity ReceiverSFAMAT01 SFA MATERIAL DOWNLOAD IDOCSHIPMENT_CHANGE01 Change ShipmentSHIPMENT_CREATEFROMDATA01 Create ShipmentSHIPMENT_CREATEFROMDATA02 Create ShipmentSHPMNT01 ShipmentSHPMNT02 ShipmentSHPMNT03 ShipmentSHPMNT04 TransportSHPMNT05 ShipmentSHP_IBDLV_CHANGE01 Change inbound deliverySHP_IBDLV_CONFIRM_DECENTRAL01 BAPI Confirmation(InboundDelivery)SHP_IBDLV_CONFIRM_DECENTRAL02 BAPI Confirmation(InboundDelivery)SHP_IBDLV_SAVE_REPLICA01 BAPI Function Module for Replication of Inbound DeliveriesSHP_IBDLV_SAVE_REPLICA02 BAPI Function Module for Replication of Inbound DeliveriesSHP_OBDLV_CHANGE01 BAPI for Change to Outbound DeliverySHP_OBDLV_CONFIRM_DECENTRAL01 BAPI Verification (OutboundDelivery)SHP_OBDLV_CONFIRM_DECENTRAL02 BAPI Verification (OutboundDelivery)SHP_OBDLV_CONFIRM_DECENTRAL03 BAPI Verification (OutboundDelivery)SHP_OBDLV_SAVE_REPLICA01 BAPI Function Module for Replication of Outbound DeliveriesSHP_OBDLV_SAVE_REPLICA02 BAPI Function Module for Replication of Outbound Deliveries

SHP_OBDLV_SPLIT_DECENTRAL01 BAPI delivery split (outbound delivery)SINGLEREMUNREQUEST_GETLIST01 Determine Documents (SingleRemunRequest)SINGLEREMUNRQS_CANCEL01 Agency Business: Cancel Vendor Billing Documents BAPISINGLEREMUNRQS_CHANGE01 Agency Business: Change Vendor Billing Documents BAPISINGLEREMUNRQS_CREATE01 Agency Business: Generate Vendor Billing Documents BAPISINGLEREMUNRQS_RELEASE01 Release to Accounting (Vendor Billing Documents)SINGLEREMUNRQS_RELEASE02 Release to Accounting (Vendor Billing Documents)SINGLESETTLEMENTREQS_GETLIST01 Determine Documents (SingleSettlementReqs)SINGLESETTRQS_CANCEL01 Agency Business: BAPI Cancel Single Settlement RequestsSINGLESETTRQS_CHANGE01 Agency Business: BAPI Change Single Settlement RequestsSINGLESETTRQS_CHANGE02 Agency Business: BAPI Change Single Settlement RequestsSINGLESETTRQS_CREATE01 Agency Business: Create Bapi Single RequestsSINGLESETTRQS_CREATE02 Agency Business: Create Bapi Single RequestsSINGLESETTRQS_RELEASE01 Release Accounting (SingleSettlementReqs)SINGLESETTRQS_RELEASE02 Release Accounting (SingleSettlementReqs)SISCSO01 SIS - Sales orderSISDEL01 SIS - deliverySISINV01 SIS - billing documentSOPGEN01 General info structure distributionSRCLST01 Source ListSRVMAS01 Service master record with textsSTTMAT01 STTMAT: Material variantsSUBMAS01 EHS: Saving Replicated SpecificationsSYIDOC01 CA-EDI: Transport of IDoc typesSYNCHRON Dummy IDoc type for synchronous communicationSYPART01 Transfer from partner profilesSYRECD01 CA-EDI: Transport of IDoc record typesSYRECD02 IDoc Interface: Transport IDoc record typesSYSTAT01 CA-EDI: Transfer from status recordsT006_01 Units of measurementTCURC_01 Currency CodesTCURR_01 Exchange ratesTEMPLATECO_CREATEFROMDATA01 CreateFromData for Business Object TemplateCOTEMPLATECO_DELETE01 Delete for Business Object TemplateCOTIMESHEETCPRCONNECT_TRANSCPR01 Transfer CATS II Data by cProjects

TIMESHEETHRCONNECTOR_DATATRA01 Transfer of CATS II Data into HRTIMESHEETLOCOCONNECT_TRACO01 Transfer of CATS II Data into PS, PM, and COTIMESHEETLOCOCONNECT_TRAPM01 Transfer of CATS II Data into PS, PM, and COTIMESHEETLOCOCONNECT_TRAPS01 Transfer of CATS II Data into PS, PM, and COTPSDLR01 Selection via variant from external systemTPSDLS01 Dispatch of delivery documents to shipping planning systemTPSLOC01 Dispatch of location master data to transport planning syst.TPSSHT01 Dispatch of planned shipments from transport planning systemTRADINGCONTRACT01 Trading Contract: Create from Template DataTRADINGCONTRACT_CHANGE01 Trading Contract: Change Template DataTRPL_PNR_IDOC IDoc Data Structure of Generic PNR (TRPL_PNR)TRXSTA02 Tracking Event MessageTXTRAW01 Transfer free text to SAPoffice format 'RAW'TXTRAW02 Transfer free text to SAPoffice format 'RAW'UNIMA2 Alternative units of measure with acquisition of materialsUNIT2 Units in CC2UNIT3 Units in CC3UNIT4 Units in CC4UPLOAD Configuration transceiver for uploadUPSMAS01 MASTER : ALE Distribution UnitUPSRCP01 RECEIPT : ALE Distribution UnitUSERACTGROUPSASSIGN01 User: Change entire activity group assignmentUSERACTGROUPSDELETE01 User: Delete entire activity group assignmentUSERCHANGE01 Change UserUSERCLONE01 Create user with template in another systemUSERCLONE02 Create user with template in another systemUSERCLONE03 Create User with Template in Another SystemUSERCLONE04 Create User with Template in Another SystemUSERCREATE01 BAPI to Create a UserUSERDELETE01 BAPI to Delete a UserUSERLOCK01 Lock UserUSERPROFILESASSIGN01 User: Assign profilesUSERPROFILESDELETE01 User: Delete All Profile AssignmentsUSERRESPONSE01 Users: Confirmation to Central SystemUSERUNLOCK01 Unlock userUSER_WPPERSDATASAVE01 Writing the WP Personalization Data for a UserVALPROJECTSTOCK_PRICECHANGE01 Material Price ChangeVALSALESORDSTOCK_PRICECHANGE01 Material Price ChangeVALSCALE01 Maintain Value and Quota scaleVCHARVAL01 maintain vendor characteristic valuesVCUI_DELETE01 BAPI: Delete Interface DesignVCUI_EXISTENCECHECK01 BAPI: Checks Whether Interface Design ExistsVCUI_SAVEM01 Create or Change Interface Design

VCUI_SAVEM02 Create or Change Interface DesignVENDCBDLIST_CHANGE01 Agency Business: Change Posting Lists BAPIVENDCBDLIST_CREATE01 Agency business: Generate Bapi posting listsVENDCBDLIST_CREATE02 Agency business: Generate Bapi posting listsVENDCBDLIST_RELEASE01 Agency Business: BAPI Release Posting Lists Document to FIVENDCBDLIST_RELEASE02 Agency Business: BAPI Release Posting Lists Document to FIVENDTRIGGEREDCBDLIST_GETLIST01 Agency Business: BAPI Determine Posting List Detailed DataVFNMAS01 Master Variant FunctionVFNMAS02 Master Variant Function + E1UPSLINKVTAMAS01 Master variants tableVTAMAS02 Master Variant Table + E1UPSLINKVTMMAS01 Master maintenance table contentsVTMMAS02 Master Maintenance for Table Contents + E1UPSLINKWALNOT01 Allocation: Allocation table notificationWALREQ01 Allocation: Report requested quantitiesWBBDLD01 Assortment list: Material dataWBBDLD02 Assortment list: material data (Rel. 4.0)WBBDLD03 Assortment lists: Material data (Rel. 99A)WBBDLD04 Assortment List: Material Data: R/3 Enterprise ReleaseWFRESOURCE_CHANGEAVAILABILIT01 Change Availability Period of a WFM ResourceWGSREQ01 Order receipt IS-RWGSREQ02 Store order IDoc (inc. condition segment)WMBIID01 Block Storage BinsWMCAID01 Reversal/Reversal request for transfer orderWMERCAT01 Merchandise Category and associated data IDocWMINID01 Information text for link to subsystemsWMIVID01 Enter count resultsWMMBID01 Goods movements for mobile data entryWMMBID02 Stock movements from ext. systemsWMPHID01 Pick HU (Handling Unit)WMRRID01 Release reference numberWMSUID01 Move storage unitWMTCID01 Confirm transfer orderWMTCID02 Confirm transfer orderWMTCID03 Confirm TOWMTOID01 Transfer orderWMTOID02 Send pick HUWMTRID01 Transfer requirementWORKC2 Workcenters in CC2WORKC3 Work centers in CC3WORKC4 Workcenters in CC4WORKSCHED_WITH_COST01 Insert Operative Planned Working Time (With Cost

Assignment)WPDBBY01 POS outbound: bonus buy conditionsWPDCUR01 POS interface: Download exchange ratesWPDNAC01 POS interface: Download productsWPDREB01 POS interface: Download special offer discountsWPDSET01 POS interface: Download set assignmentsWPDTAX01 POS interface: Download tax ratesWPDWGR01 POS interface: Download material group masterWPUBON01 POS interface: Upload sales docs (trnsctns), non-aggregatedWPUERR01 POS interface: Upload messages SRS/POS/SCSWPUFIB01 POS interface: Upload Fin.Acc. interface SRS/POSWPUKSR01 POS Interface: Inbound processing cashier data for POS statsWPUTAB01 POS interface: Upload day-end closing POSWPUUMS01 POS interface: Upload sales data (compressed)WPUWBW01 POS interface: Upload goods movementsWP_EAN01 POS interface: Upload/Download EAN assignmentsWP_PER01 POS interface: Upload/Download person dataWP_PLU01 POS interface: Upload/Download article masterWP_PLU02 POS interface: material and condition (inbound and outb.)WRMA_REV_DATA RMA revaluation data from BWWRMA_REV_REQUEST Data request for revaluation in R/3 systemWTADDI01 AdditionalsWVINVE01 Store phy.inv.: phy.inv. docs outbound; count data inboundWVINVE02 Store phy.inv.: phy.inv. docs outbound; count data inboundWVINVE03 Store phy.inv.: phy.inv. docs outbound; count data inboundW_WGRP01 Distribution of material groups