Idocs in SAP R/3
Introduction 1 Structure of an IDoc interface o 1.1 Structure of an IDoc o 1.2 Structure of a segment o 1.3 Structure of an interface 2 Customizing of an outbound interface o 2.1 Creation of a new message type o 2.2 Customizing of a new interface o 2.3 Creation of an outbound interface program 3 Additional customizings o 3.1 Filter o 3.2 IDoc reduction o 3.3 Integration of an inbound IDoc 4 Appendices o 4.1 Useful transactions for IDocs o 4.2 Standard statuses of IDoc o 4.3 List of standard basic IDoc types Conclusion
The 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.
Structure of an IDoc interface
1.1 Structure of an IDoc
A 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.
An 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.
188.8.131.52 Control section
The 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.
2 Data section
The particularity of the data section is that it contains one or many segments which are organized in a hierarchical way.1.1. 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.2. it is this section which contains the application data to transmit. because as it is implied in its name.
after its transfer into an other system.3 Status section
The particularity of the status section is that it is specific to the system where the IDoc is displayed.2. the IDoc is actually rebuilt by copy. This status section is composed of one or many status segments. so that only the last segment has a real importance. 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. In consequence. These segments are organized in a sequential way. segment by segment.
.1. The status segments only are not transfered: there are specific to each one of the systems. Indeed.1.
1 stands for outbound.2.1. from the point of view of the local system. 4 for collected sending
. 2 for inbound Status: current status of the IDoc in the local system Basic type: basic IDoc type Extension: type of extension.2 Structure of a segment
1. most of the time LS which stands for Logical System o SAP Release: version number of the IDoc Output Mode: output mode.Type: partner type. if applicable Message type: message type Sender or Recipient information: details concerning the sender or the receiver o Port: port o Partner number: number of logical system o Partn. 2 stands for immediate sending.1 Control segment
The most important fields of the control segment are the following: IDoc number: number of the IDoc in the local system Direction: direction of the IDoc.
2. every fields of every data segments have the character format. each field having a different length. Each segment type has a different number of fields. whatever the way the fields are represented in the IDoc display.2 Data segment
The structure of a data segment depends on the segment type.1. The only common characteristic between all the segment types is the format of the data.
.3 Status segment
The structure of a status segment is the following: Status: the status reported by the segment Message: the text describing the status The other fields of the status segment are used to create a message following a SAP standard structure.1.
3 Structure of an interface
An interface is made of the following elements: A view of the distribution model (optional) o No. one or many filters A sending system A receiving system A message type For outbound interfaces: o A port to emit to o An output mode o A packet size o A basic IDoc type For inbound interfaces: o A process code
3. it is possible to distribute this view to the partner system. Indeed.1.1 View of the distribution model
The creation of a view in the distribution model is optional.
. as it is also possible to generate the partner profiles for this view. 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.
. Each basic IDoc type is able to contain essential data on material master data. By convention. To this MATMAS message type is associated several basic IDoc types: MATMAS01. MATMAS01 is the first version. the MATMAS message type is related to material master data.3.2 Message type and basic IDoc type
A message type represents the group in which every basic IDoc types must belong. 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. and it is preferable to do so for all the new types to be created.) and adds fields comparing with the previous version. The standard message types and basic IDoc types in SAP R/3 respect this convention. A message type is conceptually the nature of the data transmitted within an IDoc. etc. Material Master. MATMAS03. MATMAS02. each subsequent version increments the sequence number (MATMAS02. MATMAS04 et MATMAS05. For example.
For outbound interfaces: o A port to emit to o An output mode o A packet size o A basic IDoc type For inbound interfaces: o A process code
. without replacing them though. the parameters LS / REMSYST / Outbound deal with the outbound interfaces with the REMSYST logical system. The parameters in the partner profiles are displayed with a reference frame which is the local system.3 Partner profiles
Dealing with every interfaces which do not have any filter. These parameters are different whether they affect an outbound or an inbound interface. For exemple. the views of the distribution model are there only to simplify and conceptualize the partner profiles. only the partner profiles are effective. Indeed.1.3.
Fill the Segment type field with the value Z1VISTAPM then press F5 (Create).
2.1 Creation of a new segment type
Launch the WE31 transaction (Development segments: Initial screen).1.2 Customizing of an outbound interface
This chapter approaches the creation of a new outbound interface entirely specific.1 Creation of a new message type
. It uses no one of the standard SAP R/3 structures.
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.
2. name field with the value ZVISTAPM01 then press F5 (Create).
.Save.2 Creation of a new basic IDoc type
Launch WE30 transaction (Develop IDoc Types: Initial Screen).1. Fill the Obj.
Select the ZVISTAPM01 header line then choose the Create segment.. In the popup window which appears.type: Z1VISTAPM Mandatory seg. button..In the popup window which appears.: [checked] Minimum number: 1 Maximum number: 999999
. fill the fields like the following: Segm. choose Create new and fill the Description field.
2.Save.3 Creation of a new message type
Launch the WE81 transaction (Display View "EDI: Logical Message Types": Overview).1.
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.
2.4 Association of the basic IDoc type to the message type
Launch the WE82 transaction (Display View "Output Types and Assignment to IDoc Types": Overview).1.Save.
type the value ZVISTAPM01. In the Release column. In the Message Type column. type the value ZVISTAPM.
.Choose the Display -> Change button then the New Entries button. type the value 620. In the Basic Type column.
2.2 Customizing of a new interface
.2.1 Creation of a new distribution model view
Launch the BD64 transaction (Display Distribution Model).
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. enter in the Short text field a short description and in the Technical name field the value YVISTAPM. enter in the Sender field the name of the local logical system. In the popup window which appears.Press the Switch between display and edit mode button. then the Create model view button. In the popup window which appears.
Place on the newly created entry then press the Add Message Type button.
Be careful! The partner profiles also have to be generated and managed in the partner system.
2. It allows to centralize the changes to make on the interface. there is no need to make other further selection. In the popup window which appears. place on the message type then choose in the menu Environment / Generate partner profiles.Validate then save.2 Distribute the distribution model view
This step is necessary only if the partner system is a SAP R/3 system.3 Generate and manage the partner profiles
From the distribution model view (BD64 transaction).
. or launch the BD82 transaction (Generating partner profile).2. Select the recently created view then choose in the menu Edit / Model view / Distribute. the partner system is already selected. Validate.2.
Enter in the Model view field the value YVISTAPM. and choose as Output mode the Collect IDocs and transfer radio button. in the Partner system field the value TIBCO. Press the Execute button.
If needed. The port should be checked first.
. Select LS / TIBCO / Outbound parmtrs. launch the WE20 transaction (Partner profiles). so it is the first port which is selected by default. / ZVISTAPM. To do so. manage the partner profiles then save.Check the partner profiles. because it is not specified at the generation of the partner profiles level.
MOVE C_DOCTYP TO WA_EDIDC-IDOCTP. C_SEGNAM TYPE EDIDD-SEGNAM VALUE 'Z1VISTAPM'. WA_ZVISTA_PM TYPE ZVISTA_PM_T. V_OCCMAX TYPE IDOCSYN-OCCMAX. V_NBSEG TYPE I. DATA: I_ZVISTA_PM TYPE ZVISTA_PM_T OCCURS 6000. WA_EDIDD TYPE EDIDD. C_DOCTYP TYPE EDIDC-IDOCTP VALUE 'ZVISTAPM01'. I_EDIDC TYPE EDIDC OCCURS 0. CLEAR WA_EDIDC.
FORM F_110_SEND_IDOC.2. I_EDIDD TYPE EDIDD OCCURS 0.3. WA_EDIDC TYPE EDIDC. WA_Z1VISTAPM TYPE Z1VISTAPM.1 Creation of an IDoc generation program
The following code extract contains everything needed to generate an IDoc from data contained in a table. CLEAR WA_ZVISTA_PM. CONSTANTS: C_MESTYP TYPE EDIDC-MESTYP VALUE 'ZVISTAPM'. * Save the message type and the basic IDoc type * in the control segment MOVE C_MESTYP TO WA_EDIDC-MESTYP.3 Creation of an outbound interface program
* Retrieve the maximum number of segments in the basic IDoc * type SELECT 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_T INTO CORRESPONDING FIELDS OF TABLE I_ZVISTA_PM. * Create a data segment for each line of I_ZVISTA_PM LOOP 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 segments DESCRIBE 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 function CALL 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 program
The 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 customizings
A 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.
1 Creation of an ALE object
First of all. in the Message type field. then validate. ZVISTAPM here.
Validate then save. type the message that should be filtered. An object which type will be identical to the Data Element of the field to be filtered has to be created.1.2. In the Field name field.3.
3. type the value MAKT. Launch the BD95 transaction (Change View "ALE Object Type": Overview).1. In the Table name field. an "ALE object" has to be created to be able to filter on it. A table field which the Data Element is the same like the field to be filtered should be chosen. type the value MATNR.2 Customizing 3. In the popup window which appears.
. In the ALE Object Type field.2 Association of an ALE object type to a message type
Launch the BD59 transaction (Change View "Assignment of Object Type to Message": Overview). type the value MATNR.2.1.
Validate and save. In the ALE Object Type field. type the value MATNR.2.
3. Press the Switch between display and edit mode button.
. type the value 1. field. type the value Z1VISTAPM.1.type field. type the value MATNR. In the No. In the Segm. In the Field field. develop the previously created YVISTAPM view and double-clic on the No filter set line.3 Creation of the filter in the distribution model
Launch the BD64 transaction (Display Distribution Model).Press the New Entries button.
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.
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.
.Validate twice then save. Here is your new filter active.
Launch the BD53 transaction (IDoc Reduction Maintenance: Initial Screen). which represents a dynamical method. provided that the deleted segments are not mandatory.3. The number of segments or the number of fields in a segment can also be reduced in a static way.2. then press the Create button.2 IDoc reduction
3. The segments of a reduced IDoc can also have less fields than the corresponding segments of the basic IDoc. their integration function module already takes into account the possibility of a reduction. In the Reduced message type field.
In the popup window which appears. A filter can applied (see above). Dealing with the standard basic IDoc types. However. SAP had envisaged their reduction.1 Principle
Standard basic IDoc types are often adapted to all imaginable interfaces. type the value ZVISTAPM_REDUCED.
. The advantage to use reduced IDocs seems to be obvious then: to profit from standard functions while reducing the volume of exchanged data. it sometimes happens that the sent volume is too big compared with the needs. type in the Message type reference field the value MATMAS. while still keeping the structure of the basic IDoc type.
3. A reduced IDoc has less segments than the basic IDoc.2. Indeed. for all basic IDocs.
select the segments and the fields needed for the new reduced message type.
*"Local interface: IMPORTING VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
. type a short description for the new reduced message type.3. In the following window.1 Development
Below is the prototype of the function module to develop to integrate an inbound IDoc.3 Integration of an inbound IDoc
3. Validate. In the next popup window.Validate.
1 Useful transactions for IDocs
BD87 : Status Monitor for ALE Messages SALE : Display ALE Customizing WE02 : Display IDoc WE05 : IDoc Lists WE09 : Search for IDoc in Database WE19 : Test tool
4. WE57 (Display View "IDoc: Assignment of FM to Log.2 Customizing
Below is the list of transactions to launch in order to associate the integration function module with the corresponding message type.1 Outbound IDocs statuses
.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_MESSAGE
3. 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. 2.3. These are those codes which will be specified at the partner profiles level for inbound interfaces.
4. 1.2.2 Standard statuses of IDoc
4. WE42 (Display View "Inbound process code": Overview) This transaction is used to declare the process codes for integration. 3. Message and IDoc Type": Overview) This transaction is used to associate the previously declared function module to the message type to be integrated.
acknowledgement still due Error during retransmission Control information of EDI subsystem OK Processing despite syntax error (outbound) Error during syntax check of IDoc (outbound)
.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
Not used. only R/2 IDoc generated Error passing data to port Data passed to port OK Error within control information of EDI subsystem Error during translation Translation OK Error during syntax check Syntax check OK Error during interchange handling Interchange handling OK Error during dispatch Dispatch OK Retransmission OK Interchange Acknowledgement positive Interchange Acknowledgement negative Functional Acknowledgement positive Functional Acknowledgement negative Triggering EDI subsystem OK Data transfer for test OK Error triggering EDI subsystem Error passing data for test Dispatch OK.
27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42
Error in dispatch level (ALE service) Not used Error in ALE service IDoc ready for dispatch (ALE service) Error .2.no further processing IDoc was edited Original of an IDoc which was edited Error in control record of IDoc IDoc reloaded from archive Electronic signature not performed (timeout) IDoc added incorrectly IDoc archived IDoc is in the target system (ALE service) Application document not created in target system Application document created in target system IDoc was created by test transaction
4.2 Inbound IDocs statuses
Statut Description 50 51 52 53 54 55 56 57 58 IDoc added Application document not posted Application document not fully posted Application document posted Error during formal application check Formal application check OK IDoc with errors added Test IDoc: Error during application check IDoc copy from R/2 connection
Basic type 100_01 682_01 683_01 684_01 685_01 686A_01 ABSEN1 Description Output Access sequence Pricing Procedure (only in 40c) Condition Exclusion Groups Condition type Conditions: Exclusion indicator: Attendance/Absence in CC1
. This knowledge allows him or her to put in place interfaces very quickly.3 List of standard basic IDoc types
The skills of a good IDoc interfaces manager are.59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74
Not used Error during syntax check of IDoc (inbound) Processing despite syntax error (inbound) IDoc passed to application Error passing IDoc to application IDoc ready to be transferred to application Error in ALE service IDoc is waiting for predecessor IDoc (serialization) Not used Error . without having to develop a new specific type. only R/2 IDoc archived IDoc was created by test transaction
4. for the most.no further processing IDoc was edited Original of an IDoc which was edited IDoc reloaded from archive Not used. linked to his good knowledge of standard basic IDoc types.
Reversal (OAG: LOAD RECEIVABLE) Accounting: Posting Accounting: Posting Accounting: Post Reversal FI/CO: HR Posting GL(AcctngEmplyeeExpnses) FI/CO: HR posting GL(AcctngEmplyeeExpnses) FI/CO: HR Posting AP(AcctngEmplyeePaybles) FI/CO: HR posting AP(AcctngEmplyeePaybles) FI/CO: HR Posting AR(AcctngEmplyeeRcvbles) FI/CO: HR posting AR(AcctngEmplyeeRcvbles) Accounting: General G/L Account Posting Accounting: Post General G/L Posting Reversal Accounting: Post Goods Movement (OAG: POST JOURNAL) Accounting: Post Goods Movement (OAG: POST JOURNAL) Accounting: Post Goods Movement Reversal (Acctng Goods Mvt) Accounting: Change TS posting (AcctngInvoiceReceipt) Accounting: Post Invoice Receipt (OAG: LOAD PAYABLE) Accounting: Post Invoice Receipt (OAG: LOAD PAYABLE) Accounting: Post Invoice Receipt (OAG: LOAD PAYABLE)
.ACCONF01 ACC_ACT_ALLOC01 ACC_ACT_ALLOC02 ACC_ACT_ALLOC03 ACC_ASSET_TRANSFER01 ACC_ASSET_TRANS_ACQ_POST01 ACC_BILLING01 ACC_BILLING02 ACC_BILLING_REVERSE01 ACC_DOCUMENT01 ACC_DOCUMENT02 ACC_DOCUMENT_REVERSE01 ACC_EMPLOYEE_EXP01 ACC_EMPLOYEE_EXP02 ACC_EMPLOYEE_PAY01 ACC_EMPLOYEE_PAY02 ACC_EMPLOYEE_REC01 ACC_EMPLOYEE_REC02 ACC_GL_POSTING01 ACC_GL_POSTING_REVERSE01 ACC_GOODS_MOVEMENT01 ACC_GOODS_MOVEMENT02 ACC_GOODS_MOV_REVERSE01 ACC_INVOICE_PYMNTBLK01 ACC_INVOICE_RECEIPT01 ACC_INVOICE_RECEIPT02 ACC_INVOICE_RECEIPT03
Confirmation of IDoc processing from the application Accounting: Post activity allocation Accounting: Post activity allocation Accounting: Post Activity Allocation Accounting: Post Acquisition from Transfer Accounting: Post Acquisition from Transfer Accounting: Post Billing Document (OAG: LOAD RECEIVABLE) Accounting: Post Billing Document (OAG: LOAD RECEIVABLE) Accounting: Post Billing Doc.
ACC_INVOICE_REVERSE01 ACC_MAN_ALLOC01 ACC_PRIM_COSTS01 ACC_PRIM_COSTS02 ACC_PURCHASE_ORDER01 ACC_PURCHASE_REQUI01 ACC_REVENUES01 ACC_REVENUES02 ACC_SALES_ORDER01 ACC_SALES_QUOTA01 ACC_SENDER_ACTIVITIES01 ACC_STAT_KEY_FIG01 ACC_TRAVEL01 ACLPAY01 ACLREC01 ACPJOU01 ACTIV3 ACTIV4 ACTIVITYTYPEGROUP_ADDNODE01 ACTIVITYTYPEGROUP_CREATE01 ADR2MAS01 ADR2MAS02 ADR3MAS01 ADR3MAS02 ADRMAS01 ADRMAS02 ALEAUD01
Accounging: Post Invoice Reversal (Acctng Invoice Receipt) Accounting: Post Manual Cost Allocation Accounting: Post primary costs Accounting: Post Primary Costs Accounting: Post Purchase Order Accounting: Post Purchase Requisition Accounting: Post revenues Accounting: Post Revenues Accounting: Post Sales Order Accounting: Post Customer Quotation Accounting: Post Sender Activities Accounting: Post statistical key figures Accounting: Post trip Posting in Accounting: Incoming Invoice Posting in accounting: Billing document Posting in Accounting from Materials Management Units in KK3 Units in KK4 Object BUS1115 (Activity Type Group) .Method Create BAPI for inbound distribution of private addresses BAPI for inbound distribution of private addresses BAPI for inbound distribution of contact person addresses BAPI for inbound distribution of contact person addresses BAPI for inbound distribution of organizational addresses BAPI for inbound distribution of organizational addresses Confirmations of the processing status of inbound IDocs
.Method AddNode Object BUS1115 (Activity Type Group) .
ALEREQ01 ARTMAS01 ARTMAS02 ARTMAS03 ARTMAS04 ASSETACQUISITION_POST01 ASSET_POSTCAP_POST01 ASSET_RETIREMENT_POST01 ASSMOD01 ASSORTMENT01 ATT_ABS01 ATT_ABS_WITH_ACTIVITY01 ATT_ABS_WITH_COST01 BANK_CHANGE01 BANK_CREATE01 BANK_SAVEREPLICA01 BAPIPOHISTORYFROMDELIVERY01 BATCH5 BATMAS01 BATMAS02 BATMAS03 BBPCO01 BBPIV01 BBP_IV_T01 BENEFIT1 BENEFIT2 BENEFIT3
General request ./absence: Insert in IFT (acct assgnmnt) Change bank Create bank Duplicate individual banks (ALE) Purchase Order. Att./absence (PTManagerExtAttAbs) BAPI ext. Att. Delivery Batch in CC5 Replicate batch Replicate Batch Replicate batch
BBP Create Invoice EBP Create Invoice HR: Benefits HR: Benefits Participation HR: Benefits Participation
./absence: Insert in IFT (w/o acct assgnmnt) Ext.Basis IDoc type Create and Change Material Master Data (Retail) Create and Change Material Master Data (Retail) Create and Change Material Master Data (Retail) Create and change material master data (retail) Post Asset Acquisition Post post-capitalization Post asset retirement Assortment (manual modules) Maintenance of assortments BAPI ext. Att.
BAPI: Change Address SAP BP.document Master BOM .6B) Material BOM with UPS Link Master BOM .document Master BOM .material Master BOM . BAPI: Delete Bank Details SAP BP. BAPI: Add Bank Details SAP BP. BAPI: Add Address SAP BP. BAPI: Add Identification Number
.BENEFITRET1 BETMAS01 BLAORD01 BLAORD02 BLAORD03 BLAREL01 BLAREL02 BMUMAS01 BOMDOC01 BOMDOC02 BOMMAT01 BOMMAT02 BOMMAT03 BOMMAT04 BOMORD01 BTC_ID01 BTC_ID02 BTC_ID03 BUPAFS_FS_CREATE_FRM_DATA01 BUPA_C_ADDADDRESS01 BUPA_C_ADDIDENTIFICATION01 BUPA_C_ADDSTATUS01 BUPA_C_BANKDETAIL_ADD01 BUPA_C_BANKDETAIL_CH01 BUPA_C_BANKDETAIL_REMOVE01 BUPA_C_CHANGEADDRESS01 BUPA_C_IDENTADD01
HR: Benefits Pension Schemes Site master data distribution ALE Purchasing contracts Purchasing contracts Purchasing contracts Contract release order statistics Contract release order statistics Replicate batch-specific material quantity units Master BOM . BAPI: Add Identification Number Business Partner: Add Status SAP BP.material (2) Material BOM (from 4. BAPI: Read Bank Details SAP BP. BAPI: Create Business Partner SAP BP.sales order Process order with components Production requirement from superior system Production commitment to superior system SAP BP.
BAPI: Change Central Data
. BAPI: Delete Identification Numbers SAP BP.BUPA_C_IDENT_REMOVE01 BUPA_C_INDUSTRYSADD01 BUPA_C_INDUSTRYS_REMOVE01 BUPA_C_PASSWORD_CH01 BUPA_C_PASSWORD_CR01 BUPA_C_PASSWORD_DELETE01 BUPA_C_PASSWORD_INIT01 BUPA_C_REMOVEADDRESS01 BUPA_C_ROLEADD01 BUPA_C_STATUS_REMOVE01 BUPA_C_TAXNUMBERADD01 BUPA_C_TAXNUM_CHANGE01 BUPA_C_TAXNUM_REMOVE01 BUPA_FS_ADDADDITIONALDATA01 BUPA_FS_ADDADDRESS01 BUPA_FS_ADDADRESSUSAGE01 BUPA_FS_ADDBANK01 BUPA_FS_ADDCUSTOMFIELDS01 BUPA_FS_ADDDIFFTYPE01 BUPA_FS_ADDEMPLOYM01 BUPA_FS_ADDEXTERNID01 BUPA_FS_ADDFISCYEAR01 BUPA_FS_ADDRATING01 BUPA_FS_ADDREPORTING01 BUPA_FS_ADDTREASURY01 BUPA_FS_BANK_REMOVE01 BUPA_FS_CHANGE01
SAP BP. BAPI: Delete Address SAP BP. BAPI: Delete Industry Data Change Password of Business Partner Internet Users Create B2C Internet User for Business Partner Delete a Business Partner Internet User Initialize Password for Business Partner Internet User SAP BP. BAPI: Add Industries SAP BP. BAPI: Add Role Business Partner: Delete Status BAPI Add Tax Number Change Tax Number Delete Tax Number Add More Data to a Business Partner Create Address (FS Business Partner) Create Address Usage BAPI for Adding Bank Attributes Create Employment Data for Business Partner Create Differentiation Type-Dependent Attributes ADD Bapi for Business Partner Employment Data Create an External Identification Number BAPI: Create Fiscal Year Information Business Partner: Ratings Create Reporting Data for a Business Partner Bapi to Create FS BuPa Attributes REMOVE BAPI for Bank Data SAP BP.
BUPA_FS_CHANGEADDITIONALDATA01 BUPA_FS_CHANGEADRESSUSAGE01 BUPA_FS_CHANGEBANK01 BUPA_FS_CHANGECUSTOMFIELDS01 BUPA_FS_CHANGEDIFFTYPE01 BUPA_FS_CHANGEEMPLOYM01 BUPA_FS_CHANGEFISCYEAR01 BUPA_FS_CHANGERATING01 BUPA_FS_CHANGEREPORTING01 BUPA_FS_CHANGETREASURY01 BUPA_FS_CHGADDRESS01 BUPA_FS_REMADDRESS01 BUPA_FS_REMOVEADDITIONALDATA01 BUPA_FS_REMOVEADRESSUSAGE01 BUPA_FS_REMOVECUSTOMFIELDS01 BUPA_FS_REMOVEDIFFTYPE01 BUPA_FS_REMOVEEMPLOYM01 BUPA_FS_REMOVEEXTERNID01 BUPA_FS_REMOVEFISCYEAR01 BUPA_FS_REMOVERATING01 BUPA_FS_REMOVEREPORTING01 BUPA_FS_REMOVETREASURY01 BUS1151_CREATE01 BUS1501_CREATE01 BUS1502_CREATE01 BUS1503_CREATE01 BUS1504_CREATE01
Change Additional Data for a Business Partner Change Address Usage Change in Bank Relationships Change Employment Data for Business Partner Change Differentiation Type-Dependent Attributes CHANGE Bapi for Business Partner Employment Data BAPI: Change Fiscal Year Information Business Partner: Change Ratings Change Reporting Data for a Business Partner Change Business Partner Attribute (BusinessPartnerFS) Change Address (FS Business Partner) Delete Address (FS Business Partner) Delete Additional Data for a Business Partner Delete Address Usage Delete Employment Data for Business Partner Delete Differentiation Type-Dependent Attributes CHANGE Bapi for Business Partner Employment Data Delete an External Identification Number BAPI: Delete Fiscal Year Information Business Partner: Delete Ratings Delete Reporting Data for a Business Partner Delete Business Partner Attribute (BusinessPartnerFS) Create Architectural Object Create Business Entity Create property Create building Create Rental Object
Create Master characteristic basic data Master attribute with object dependencies Distribute Characteristics with Dependencies and Long Texts Distr. of Characteristics with Dependencies and Long Texts BAPI for Classification: Create Assignment (Key) Create Class BAPI Class Hierarchy BAPI: Create Assignment Class Hierarchy BAPI: Create Hierarchy (Top Down)
Create Real Estate Contract SAP BP. Key Figure Planning: Postings Primary Cost Planning: Postings CATS: Change data records CATS: Change data records CATS: Delete data records CATS: Insert data records CATS: Insert data records Rough-cut planning profile Duplicate company address in another system BAPI for Characteristics .Method Create Commission Case Application CACS00 Activity input planning: Posting Activity Input Planning: Posting Activity/Price planning: Posting Activity/Price Planning: Posting Stat.Method AddNode BUSINESSPROCESSCOGRP_CREATE01 CACS00 CAP_ACTIN01 CAP_ACTIN02 CAP_ACTOUT01 CAP_ACTOUT02 CAP_KEYFIG01 CAP_PRIMCOST01 CATS_CHANGE01 CATS_CHANGE02 CATS_DELETE01 CATS_INSERT01 CATS_INSERT02 CBPRCP01 CCLONE01 CHARACTERISTIC_CREATE01 CHRMAS01 CHRMAS02 CHRMAS03 CHRMAS04 CLASSIFICATION_CREATE01 CLASS_CREATE01 CLASS_CREATESUBCLASSALLOCATI01 CLASS_CREATESUBSTRUCTURE01 Object BUS1114 (Business Process Group) . BAPI: Create Business Partner
BUSINESSPROCESSCOGRP_ADDNODE01 Object BUS1114 (Business Process Group) .
and E1UPSLINK TR-CM: Invitation to TR-CM system to send data TR/CM-IDOC: Transfer of TR-CM data Master configuration profile Master configuration profile Master Configuration Profile + E1UPSLINK Replicate individual business process (ALE) ALE: replicate price from business processes
COABC_BUSPROCSTRUCTURE_CREAT01 Create process struct. Document Links.CLFMAS01 CLFMAS02 CLSMAS01 CLSMAS02 CLSMAS03 CLSMAS04 CMREQU01 CMSEND01 CNPMAS01 CNPMAS02 CNPMAS03 COABCM01 COABCV01
Master object classification Master object classification Master class Distribution of classes with object dependencies Classes with long texts and document links Classes with Long Texts.(BusProcStructureCO) COACOR01 COACTV01 COAMAS01 COCOKA01 CODCMT01 COELEM01 COGRP01 COMM_ITEM01 CONDA201 CONDAT01 CONDAT02 COND_A01 COND_A02 Core master activity type IDoc for cost center/activity type Master activity type Control segment CO object/cost element IDoc for a CO document Cost elements: Master data distribution IDoc for CO groups (e. ALE condition records
.g. cost center groups) Commitment Item Master ALE Customizing Distribution Add-On Change to customizing data Distribution of Control Data Interchange of conditions: Master data for price determ.
COND_A03 CONF11 CONF21 CONF31 CONF32 CONF41 CONF42 CONF51 CONF_ACT1001 COPAGN01 COPA_DERIVE_ADD_VALUES01 COPA_DERIVE_REMOVE01 COPA_WW_ADD_VALUES01 COPA_WW_GET_VALUES01 COPA_WW_REMOVE_VALUES01 COPCPA01 COPCPA02 COSCOR01 COSMAS01 COSTCENTERGROUP_ADDNODE01 COSTCENTERGROUP_CREATE01 COSTELEMENTGROUP_ADDNODE01 COSTELEMENTGROUP_CREATE01 COTOTL01 CO_ABC_BPROC_CREATE01 CO_ABC_BPROC_SETSTRUC01 CRECOR01
Conditions with UPS Link Confirmations in CC1 Confirmations in KK2.Method AddNode Object BUS1112 (Cost Center Group) .Method AddNode Object BUS1113 (Cost Element Group) .Method Create Object BUS1113 (Cost Element Group) .Method Create IDoc for CO totals records Create one or more business processes Enter template in business process master data Vendor master data distribution ALE Core master data
. time events Confirmations in KK3. wage slips Confirmations in KK4. time events Confirmations in KK4. wage slips CC5 PDC Interface KANBAN Enter activity confirmation CO-PA entry Derivation Rule: AddValues Derivation Rule: RemoveValues Individual Characteristic: AddValues Characteristic: GetValues Individual Characteristic: RemoveValues Transfer product costing CO-PC -> CO-PA Copy product cost estimate Core master cost center Master cost center Object BUS1112 (Cost Center Group) . time events Confirmations in KK3.
customer Customer master Customer master Customer master Customer master data distribution Customer Master Data Distribution Customer master data distribution MDM: Mass-enabled DEBMAS (Customer Master) MDM: Mass-enabled DEBMAS (Customer Master) MDM: Mass Processing DEBMAS (Customer Master + Addresses)
.CREMAS01 CREMAS02 CREMAS03 CREMAS04 CREMDM01 CREMDM02 CREMDM03 CREMDM04 CRESTA01 CUSTOMERRETURN_CONFIRMDELIVE01
Vendor master data distribution ALE Vendor master data distribution ALE Vendor master data distribution Vendor master data distribution MDM: Mass Processing CREMAS (Vendor Master) MDM: Mass Processing CREMAS (Vendor Master + Addresses) MDM: Mass Processing CREMAS (Vendor Master + Addresses) MDM: Mass Processing CREMAS (Vendor Master + Addresses) Copy credit status (DebtorCreditAccount) Delivery Confirmation (CustomerReturn)
CUSTSCHEDULAGREEMENT_CONFDEL01 Delivery Confirm. (CustSchedulAgreement) CUSTSCHEDULAGREEMENT_CONFIRM01 Delivery Confirmation (CustSchedulAgreement) DANGEROUSGOOD01 DANGEROUSGOOD02 DD01L_01 DD03L_01 DD04L_01 DEBCOR01 DEBMAS01 DEBMAS02 DEBMAS03 DEBMAS04 DEBMAS05 DEBMAS06 DEBMDM01 DEBMDM02 DEBMDM03 Dangerous goods: Save replicated instances Dangerous goods: Save replicated instances Domains Table Fields Data elements Core master .
DEBMDM04 DEBMDM05 DEBMDM06 DELFOR01 DELFOR02 DELIVERYPROCESSING_EXECUTE01 DELVRY01 DELVRY02 DELVRY03 DEPNET DEPNET02 DESADV01 DES_ID01 DIFFE2 DIFFE3 DIFFE4 DISPUTE_ATTRIBUTESCHANGE01 DISPUTE_CREATE01 DISPUTE_PROCESS01 DISPUTE_STATUSCHANGED01 DISPUTE_WRITEOFF01 DISTU2 DOCMAS01 DOCMAS02 DOCMAS03 DOCMAS04 DOCMAS05
MDM: Mass Processing DEBMAS (Customer Master + Addresses) MDM: Mass Processing DEBMAS (Customer Master + Addresses) MDM: Mass Processing DEBMAS (Customer Master + Addresses) Delivery schedule/JIT schedule Delivery Schedule/JIT Schedule Delivery processing Delivery interface Delivery interface with dangerous goods data Delivery interface Master data of dependency net Master Data of a Dependency Net + E1UPSLINK External service agent processing (notifications) Shipping notification Differences in KK2 Differences in KK3 Differences in KK4 FSCM-DM: Change Dispute Case Attributes FSCM-DM: Creation of Dispute Case FSCM-DM: Process Dispute Case FSCM-DM: Change Status of Dispute Case FSCM-DM: Dispute Cases to be Written Off Automatically Reasons for problems KK2 Master document Document 02 Document Documents Documents with UPS Link
.DOCUMENT_LOAD01 DOLMAS01 DOLMAS02 DSPMAS01 DSPRCP01 DWLOAD DXPROJECT_CREATE01 DXPROJECT_CREATE02 DXPROJECT_CREATE03 DXTCRE01 ECMMAS01 ECMMAS02 ECMREV01 EEWAGECOMP_CHANGE01 EEWAGECOMP_CREATE01 EEWAGECOMP_DELETE01 EHPOST01 EKSEKS01 EMPWAGECOMPEXT_CHANGE01 EMPWAGECOMPEXT_CREATE01 EMPWAGECOMPEXT_DELETE01 EQUIPMENT_CHANGE01 EQUIPMENT_CREATE01 EVMSTA01 EVMSTA02 EXCHANGE_RATE01 EXPINV01
Load document data (Document transfer) Document-object links Document-Object Links with UPS Link ALE Distribution Packet ALE Distribution Packet Download transceiver configuration Create Method of Business Object DXPROJECT Create Method of Business Object DXPROJECT Create Method of Business Object DXPROJECT Object SBFADXT IDoc structure for ECH Change number (II) IDOC structure for revision level Modification of External Wage Component Creation of Infotype Record for External Wage Component Deletion of External Wage Component SCEM: Event Handler Posting Purchasing document data for Purchasing Info System Modification of External Wage Component Creation of External Wage Component Deletion of External Wage Component PM BAPI: Change Equipment PM BAPI: Create Equipment SCEM: Event Message Input SCEM: Event Message Input Replication of Currency Rates Export Invoice IDOC (E.F.I.
Billing Doc.billing doc. Lockbox.billing doc. IDoc Create External Security Account Statement External wage types IDoc for FI document changes (dunning block) IDoc: Complete FI document FI IDoc: Complete FI Document IDoc for FI documents Create security Create financial transaction Account Statement.EXPINV02 EXPINV03 EXPINV04 EXTSECURITYACCSTMNT_CREATE01 EXTWA1 FIDCCH01 FIDCCP01 FIDCCP02 FIDCMT01 FINANCIALPRODUCT_CREATE01 FINANCIALTRANSACTION_CREATE01 FINSTA01 FIPARQ01 FIXEDASSET_CHANGE01 FIXEDASSET_CHANGE02 FIXEDASSET_CHANGE03 FIXEDASSET_CREATE01 FIXEDASSET_CREATE02 FIXEDASSET_CREATEFROMDATA101 FIXEDASSET_CREATEFROMDATA102 FIXEDASSET_CREATEINCLVALUES01 FIXEDASSET_CREATEINCLVALUES02 FLCUSTOMER_CREATEFROMDATA01 FLIGHTBOOKING_CANCEL01 FLIGHTBOOKING_CONFIRM01 FLIGHTBOOKING_CREATEFROMDAT01 FLIGHTCUSTOMER_CHANGE01
Foreign Trade . Polling Info IDoc for FI payment data Changes an asset Changes an asset Changes an Asset Creates an asset Creates an asset Creates an Asset Creates an Asset BAPI for Legacy Data Transfer BAPI for Legacy Data Transfer Create new customer Cancel flight booking Confirm flight booking Create flight booking Change Flight Customer
. IDoc Foreign trade . IDoc Foreign trade .
Change RFC for Method Condition.Create' FTR: RFC for Method 'Paymentdetail.Create' FTR: RFC for Method 'Paymentdetail.Create' FTR: RFC for Method 'Paymentdetail.Create RFC for Method Condition.Delete RFC for Method Condition.GetList Counterconfirm financial transaction Change Commercial Paper Create Commercial Paper Details of a fixed-term deposit Reverse Fixed-Term Deposit per BAPI Change fixed-term deposit per BAPI
.Create' FTR: RFC for Method 'Paymentdetail.CashflowGetList' Details of a cash flow-dependent transaction Reverse Cash Flow-Dependent Transaction RFC for Method Condition.Delete' FTR: RFC for Method 'Paymentdetail.FLIGHT_SAVEREPLICA01 FTDABA01 FTDACU01 FTRCON01 FTRPAYMENTDETAIL_GETLIST01 FTR_ADDFLOW_CHANGE01 FTR_ADDFLOW_CREATE01 FTR_ADDFLOW_DELETE01 FTR_ADDFLOW_GETLIST01 FTR_CFT_CHANGE01 FTR_CFT_CREATE01 FTR_CFT_FLOWCHANGE01 FTR_CFT_FLOWCREATE01 FTR_CFT_FLOWDELETE01 FTR_CFT_FLOWGETLIST01 FTR_CFT_GETDETAIL01 FTR_CFT_REVERSE01 FTR_CONDITION_CHANGE01 FTR_CONDITION_CREATE01 FTR_CONDITION_DELETE01 FTR_CONDITION_GETLIST01 FTR_COUNTERCONFIRM01 FTR_CP_CHANGE01 FTR_CP_CREATE01 FTR_CP_GETDETAIL01 FTR_CP_REVERSE01 FTR_DAN_CHANGE01
Save replicated flight data Foreign Trade Data Service Basic Data Foreign Trade Data Service Customs Data Confirm transaction List of Payment Details FTR: RFC for Method 'Paymentdetail.Delete' FTR: RFC for Method 'CFT.Create' Change Cash Flow-Dependent Transaction Create Cash Flow-Dependent Transaction FTR: RFC for Method 'Paymentdetail.
Create' Reverse Fixed-Term Deposit per BAPI Roll Over Fixed-Term Deposit per BAPI Change fixed-term deposit per BAPI Create fixed-term deposit Details of a fixed-term deposit FTR: RFC for Method 'FinancialTransaction.Delete' FTR: RFC for Method 'Paymentdetail.Delete' FTR: RFC for Method 'Paymentdetail.Create' FTR: RFC for Method 'Paymentdetail.Create' Reverse Fixed-Term Deposit per BAPI Roll Over Fixed-Term Deposit per BAPI Change an FX Option Create Currency Option Exercise FX Option Allow FX Option to Expire Details on FX Options Knockin FXOPTION Knockout FXOPTIONS Reverse FX Option Cancel FX OPTION
.Create' FTR: RFC for Method 'Paymentdetail.MainFlowCreate' FTR: RFC for Method 'Paymentdetail.MainFlowCreate' FTR: RFC for Method 'Paymentdetail.FTR_DAN_CREATE01 FTR_DAN_GETDETAIL01 FTR_DAN_GIVENOTICE01 FTR_DAN_MAINFLOWCHANGE01 FTR_DAN_MAINFLOWCREATE01 FTR_DAN_MAINFLOWDELETE01 FTR_DAN_MAINFLOWGETLIST01 FTR_DAN_REVERSE01 FTR_DAN_ROLLOVER01 FTR_FTD_CHANGE01 FTR_FTD_CREATE01 FTR_FTD_GETDETAIL01 FTR_FTD_MAINFLOWCHANGE01 FTR_FTD_MAINFLOWCREATE01 FTR_FTD_MAINFLOWDELETE01 FTR_FTD_MAINFLOWGETLIST01 FTR_FTD_REVERSE01 FTR_FTD_ROLLOVER01 FTR_FXOPTION_CHANGE01 FTR_FXOPTION_CREATE01 FTR_FXOPTION_EXERCISE01 FTR_FXOPTION_EXPIRE01 FTR_FXOPTION_GETDETAIL01 FTR_FXOPTION_KNOCKIN01 FTR_FXOPTION_KNOCKOUT01 FTR_FXOPTION_REVERSE01 FTR_FXOPTION_SETTLE01
Create fixed-term deposit Details of a fixed-term deposit Roll Over Fixed-Term Deposit per BAPI FTR: RFC for Method 'FinancialTransaction.
Delete' FTR: RFC for Method 'Paymentdetail.Create' Reverse interest rate instrument FTR: RFC for Method 'Paymentdetail.Delete' FTR: RFC for Method 'Paymentdetail.Create' FTR: RFC for Method 'Paymentdetail.Create' Change security transaction Create security transaction Security transaction details Reverse Security Transaction Settle Security Transaction Settle financial transaction
.MainFlowCreate' FTR: RFC for Method 'Paymentdetail.FTR_FXT_CHANGE01 FTR_FXT_CREATE01 FTR_FXT_GETDETAIL01 FTR_FXT_REVERSE01 FTR_FXT_SETTLE01 FTR_FX_CREATESWAP01 FTR_FX_CREATESWAP011 FTR_GETDETAIL01 FTR_GETLIST01 FTR_IRATE_CHANGE01 FTR_IRATE_CREATE01 FTR_IRATE_GETDETAIL01 FTR_IRATE_MAINFLOWCHANGE01 FTR_IRATE_MAINFLOWCREATE01 FTR_IRATE_MAINFLOWDELETE01 FTR_IRATE_MAINFLOWGETLIST01 FTR_IRATE_REVERSE01 FTR_PAYDET_CHANGE01 FTR_PAYDET_CREATE01 FTR_PAYDET_DELETE01 FTR_PAYDET_GETLIST01 FTR_SECURITY_CHANGE01 FTR_SECURITY_CREATE01 FTR_SECURITY_GETDETAIL01 FTR_SECURITY_REVERSE01 FTR_SECURITY_SETTLE01 FTR_SETTLE01
Change forex transaction Create forex transaction Details of a forex transaction Reverse forex transaction Settle Forex Transaction Create Forex Transaction Create Currency Swap Read transaction detailed data Read transaction list Change interest rate instrument Create interest rate instrument Create interest rate instrument FTR: RFC for Method 'FinancialTransaction.Create' Create Payment Details FTR: RFC for Method 'Paymentdetail.
/absence reasons CC1: Download Employee Balances CC1: Download Cost Centers CC1: Download permitted external wage types CC1: Download Internal Orders CC1: Download Objects (such as Positions) CC1: Download HR Mini-Master CC1: Download Time Event Type Groups CC1: Download Work Breakdown Structure Element CC1: Upload Request for Employee Expenditures CC1: Upload Request for Time Events CC1: Upload external wage types CC1: Upload time events Transfer confirmations (TimeMgtConfirmation) HR TIM CC1: Allowed Attedance/Absence Reasons HR TIM CC1: External Wage Types Confirmation
.FUNC_LOC_CHANGE01 FUNC_LOC_CREATE01 FUNDMA01 FUNDSCTR GLCORE01 GLDCMT01 GLMAST01 GOODSMVT_SAPCREATE01 GSVERF01 GSVERF02 GSVERF03 HRCC1DNATTAB01 HRCC1DNBALAN01 HRCC1DNCOSTC01 HRCC1DNEXTWT01 HRCC1DNINORD01 HRCC1DNOBJID01 HRCC1DNPERSO01 HRCC1DNTEVGR01 HRCC1DNWBSEL01 HRCC1REQUPEXTWT01 HRCC1REQUPTEVEN01 HRCC1UPEXTWT01 HRCC1UPTEVEN01 HRCNF01 HRKK1ABSR HRKK1EWUP
PM BAPI: Change Functional Location PM BAPI: Create Functional Location IDoc: Funds Management Fund FundsManagement: Funds Center Documentation deleted IDoc type for GLX rollups Master data G/L accounts: Max. memo procedure CC1: Download permitted att. IDoc SAP Internal Cross-System Flow of Goods IDoc input credit memo procedure Cred. memo procedure Cred.
HRKK1EXWT HRKK1PERS HRKK1TBAL HRKK1TEUP HRKK1TEVT HRKK1WRKC HRMASTER01 HRMASTER02 HRMD_A01 HRMD_A02 HRMD_A03 HRMD_A04 HRMD_A05 HRMD_A06 HRMD_ABA01 HRMD_ABA02 HRMD_ABA03 HRMD_ABA04 HRMD_B01 HRMD_B02 HRMD_B03 HRMD_B04 HROT558D HROTIN HROTUSTR HROT_BRM HROT_CAM
HR TIM CC1: Permitted External Wage Types HR TIM KK1: HR Mini Master for Time Recording HR TIM CC1: Employee Time Balances HR TIM KK1: Confirmation of person time events HR TIM CC1: Permitted Time Event Types HR TIM CC1: Permitted Work Centers Replicate (HRMasterDataReplica) Replicate (HRMasterDataReplica) HR: Master and organizational data (application system) HR: Master and organizational data (application system) HR: Master and organizational data (application system) HR: Master and organizational data (application system) HR: Planning and HR Master Data (Application System) HR: Planning and HR Master Data (Application System) HR: Master & Organizational Data (Application Basis System) HR: Master and Plan Data (Application Basis System) HR: Plan & Personnel Master Data (Application Basis System) HR: Plan & Personnel Master Data (Application Basis System) HR: Master and organizational data (basis system) HR: Master and organizational data (basis system) HR: Master and Planning Data (Basis System) HR: Master and Planning Data (Basis System) HR: Outsourcing US: Inbound IDOC Table T558A (Test) HR: Outsourcing: Inbound Payroll Results HR-PY-US : Tax Remittance Outsourcing HR: BR Master data payroll outsourcing HR: Canadian Master Data Payroll Outsourcing
The Netherlands Gross payroll outsourcing .Outsourcing HR: FR Master data payroll outsourcing HR: GB Master data payroll outsourcing HR: IE Master data payroll outsourcing HR: IT Master data payroll outsourcing Master Data Outsourcing .HROT_CAP HROT_CHM HROT_DEM HROT_ESM HROT_FIM HROT_FRM HROT_GBM HROT_IEM HROT_ITM HROT_NLM HROT_NLP HROT_TM HROT_USM HROT_USP HROT_USTP HROT_USTQ HROT_USTY HROT_XXM HROT_XXP HRPAYP01 HRPLL40 HRSM_A01 HRSM_A03 HRSM_B01 HRSM_C01 HRSM_D01 HRTRPR01
Payroll Outsourcing .Transfer FI/CO Logistics confirmations for Human Resource Management HR: HR data for personnel actions HR: HR data for personnel actions HR: Confirmation for personnel actions HR: Download TIme Data HR: Time Data Upload Transfer TRV-PAY(PayrollTravelExpenses)
.Periodic Outsourcing: US Tax Services .Quarterly Outsourcing: US Tax Services .The Netherlands HR: Outsourcing Time Wage Types HR: US Master Data Payroll Outsourcing HR: Generic US Payroll Outsourcing Outsourcing: US Tax Services .Yearly Reporting HR: International Master Data Payroll Outsourcing HR: Generic International Payroll Outsourcing HR .Canada HR: CH Master data payroll outsourcing HR: DE Master data payroll outsourcing HR: ES Master data payroll outsourcing HR: FI Master Data Payroll Export .
signature Unplanned material issues Measurement reading IDOC Import Basis IDoc (I.HRTRVL01 HRTRVL03 HR_INBND HU_CREATE01 HU_DELETE01 HU_PACK01 HU_PROCESSOUTPUTDIRECT01 HU_REPACK01 HU_UNPACK01 IDCREF01 IMATIS01 IMEASR01 IMPINV01 IM_PROGDEF_SAVEREPLICA01 INFREC01 INFRECMASS01 INOTIF01 INSPECTIONPLAN_CREATE01 INTERNALORDERGROUP_ADDNODE01 INTERNALORDERGROUP_CREATE01 INTERNAL_ORDER01 INTERNAL_ORDER_CREATE01 INTERNAL_ORDER_CREATE02 INTUPD01 INVCON01 INVOIC01 INVOIC02
HR-TRV: Transfer travel expenses FI/CO HR-TRV: Transfer Trip Costs to Payroll HR: OUTSOURCING: Inbound IDoc Tables Create handling unit with items BAPI for deleting handling units BAPI for packing an item into an HU Select and process handling-unit outputs Repack HUs and HU items BAPI for unpacking an item from an HU Reference message as logical grouping for electron.Method AddNode Object BUS1117 (Order Group) .I.) Method 'SaveReplica' for ExpenditureProgDef Purchasing info record Purchasing Info Records (Mass IDOC) Notification IDOC Create Inspection Plan Object BUS1117 (Order Group) .B.Method Create Replicate individual internal order (ALE) Create internal order from transferred data Create Internal Order From Transferred Data Notification status update IDoc Stock change data for inventory controlling Invoice/Billing document Invoice/Billing document
Operating Exp Statement Joint Venture Billing .Invoice Kanban Call for Kanban With SD Delivery Master Dependency Basic Data Master Dependency Basic Data ISR labeling: label Distribution of Layout Modules Listing conditions LIS inbound interface for external data Location in KK5 Master bill of material Master calendar Storage location stock material Number of IDocs sent IDOC for product group Master planned order Master production order Master hierarchy/networks Master routing Master routing
.INV_ID01 IOAUPD01 IORDER01 IORUPD01 IWKCEN01 JOBROLE_CLONE01 JV_EXP01 JV_EXP02 JV_INV01 KANBAN01 KNOMAS01 KNOMAS02 LABELS00 LAYMOD01 LIKOND01 LIS_EXTR LOCAT5 LOIBOM01 LOICAL01 LOIMSO01 LOINUM01 LOIPGR01 LOIPLO01 LOIPRO01 LOIRNH01 LOIROU01 LOIROU02
Invoice Work order assignments IDOC SM/PM order IDoc Order status update IDoc Work Center IDOC Create a user (job role) Joint Venture Billing .Operating Expenditure Statement Joint Venture Billing .
LOIRSH01 LOISTD01 LOITMX01 LOIWCS01 LOIWCS02 LPIEQU01 LPIPCM01 MALFK5 MANAGEREXTPAYROLL_INSERTLEGA01 MANAGEREXTPAYROLL_INSERTOUT01 MATCOR01 MATERIALBOM_CREATEBOMGROUP01 MATERIALPHYSINV_COUNT01 MATERIALPHYSINV_CREATEMULTIP01 MATERIALPHYSINV_POSTDIFFEREN01 MATERIALRESERVATION_CREATE101 MATERIALRESERVATION_DELETE01 MATERIALVALUATION_PRICECHANG01 MATMAS01 MATMAS02 MATMAS03 MATMAS04 MATMAS05 MATMAS_BAPI01 MATMAS_MASS_BAPI01 MATQM01 MATTYPE01
Master run schedule header Master requirements/stock list Transition matrix Master work center Master work center IDoc IDoc: quota arrangement Production campaign CC5 reasons for scrap Transfer payroll account Update of a payroll result using an outsourcer Core master material Creation of a material BOM group Enter Inventory Count (MaterialPhysInv) Create physical inventory document Post Differences (MaterialPhysInv) BAPI to Create Individual Reservations BAPI to Delete Individual Reservations Material Price Change Material Master Material Master Material Master Material Master Enhancement: Distribution of Single-Level Variants Create and Change Material Master Data BAPI for Mass Maintenance of Material Data Replication of QM Inspection Setup Material Types
MBGMCA01 MBGMCR01 MBGMCR02 MC1_01 MDMFDB01 MDMMETA MDMRECEIPT01 MDMREQUEST01 MDMVERA MDM_EQUIPMENT_SAVEREPLICA01 MDM_FUNCLOC_SAVEREPLICA01 MMADDI01 MRESCR01 OBDLV_PROCOUTP01 OPERA2 OPERA3 OPERA4 OPERS3 OPERS4 ORDERS01 ORDERS02 ORDERS03 ORDERS04 ORDERS05 ORD_ID01 ORGMASTER01 OSTAT2
Reverse goods movements with MB_CANCEL_GOODS_MOVEMENT BAPI Posting of goods mvts with MB_CREATE_GOODS_MOVEMENT Post goods movements with MB_CREATE_GOODS_MOVEMENT Condition tables MDM: Feedback Idoc (Object status) MDM Metadata MDM Receipt MDM Request MDM Verification SFLIGHT BAPI for Mass Maintenance of Equipment
Create and change additionals (retail) Create reservation Process delivery output without list Operations in KK2 Processes in KK3 Operations in KK4 Operation status in KK3 Operation status in KK4 Purchasing/Sales Purchasing/Sales Purchasing/Sales Purchasing/Sales Purchasing/Sales Req./quotation/purchase order/order change BAPI for replication of HR organizational data Process status CC2
Key Figures Plants in CC3 Plants in CC4
.PALMAT01 PAYMENTREQUEST_CANCEL01 PAYMENTREQUEST_CREATE01 PAYMENTREQUEST_POST01 PAYMENTREQUEST_RELEASE01 PAYMENTREQUEST_STARTPAYMENT01 PCHEAD01 PCITEMS01 PDTCO_POSTPRIMARY01 PEROP2 PERSO1 PERSO2 PERSO3 PERSO4 PEXR2001 PEXR2002 PHRMAS01 PIECEOFEQUIPMENT_DISMANTLEAT01 PIECEOFEQUIPMENT_INSTALLATFU01 PKHD5 PKPS5 PKST5 PLANDATATRANSFERCO_POSTACTIO01 PLANDATATRANSFERCO_POSTACTIV01 PLANDATATRANSFERCO_POSTKEYFI01 PLANT3 PLANT4
Plant assignment to material BOM Cancelation of a Payment Request Creation of a Payment Request Posting a Parked Payment Request Payment Request Released for Payment Start Payment of Payment Request Replicate basic and structure data of a product catalog Replicate item data of a product catalog Transfer of Planning Data: Post Primary Costs
Personnel master records in CC1 Personnel master in CC2 Personnel master in CC3 Personnel master in CC4 Payment/payment advice note/credit memo/debit advice Payment/payment advice note/credit memo/debit advice EHS: Saving Replicated Phrases Dismantle equipment at functional location Install equipment at functional location CC5 kanban control cycles CC5 Kanban container CC5 status for kanban container Planning Data Transfer: Post Activity Planning Planning Data Transfer: Post Activity Input Transfer of Planning Data: Post Stat.
Insert) Transfer time event confirmations from PDC system Transfer time ticket confirmations from PDC system Send production orders to PDC system Send work centers to PDC system Send upload request to PDC system Maintain or Create Process Structure Maintain or Create Line Balances Maintain or Create Product Structure Maintain or Create Factory Layout Create and Change Generic Engineering Node Create or Change iPEE Production Model Maintain or Create iPPE Object Resources Nodes Replicate PCA line items (ALE) Delete profit center documents (ALE) Replicate EC-PCA plan line items (ALE) Reversal of existing document line items (ALE) Profit center master record
.PORDCH01 PORDCR01 PORDCR02 PORDCR03 PORDCR04 PORDCR05 PORDCR101 PORDGD01 PO_DELETEPOHISTORY01 PO_UPDATEPOHISTORY01 PPCC2PRETEVENT01 PPCC2PRETTICKET01 PPCC2RECORDER01 PPCC2RECWORKCENTER01 PPCC2REQCONF01 PPE_ACT01 PPE_BAL01 PPE_CMP01 PPE_FLO01 PPE_GEN01 PPE_PRM01 PPE_RES01 PRCDOC01 PRCDOCD01 PRCDOCP01 PRCDOCR01 PRCMAS01
Change purchase order Create purchase order Create purchase order Create purchase order Create purchase order Create Purchase Order Create Purchase Order Display Purchase Order Details Delete Purchase Order History Update Purchase Order (Update.
PRCMAS02 PRDCAT01 PRDPOS01 PREQCR01 PREQCR02 PREQCR03 PREQDL01 PRICAT01 PRICAT02 PRICECATALOGUE01 PRICECATALOGUE02 PROACT01 PROFITCENTERGROUP_ADDNODE01 PROFITCENTERGROUP_CREATE01 PROFITCENTER_CHANGE01 PROFITCENTER_CREATE01 PROJECT01 PROMOTION_CONFIRMREQUEST01 PTOVERVIEW01 QALITY01 QALITY02 QPGR01 QPMK01 QSMT01 RCYINF01 RCYSYS01 REDEMPTIONFACTORS_CHANGE01
Profit Center master record (with company code assignment) Product catalog Product catalog item Create purchase requisition Create purchase requisition Create Purchase Requisition Delete/close purchase requisition Price/sales catalog Price List/Sales Catalog Store price catalog instance Save Price Catalog Instance Transfer of stock and sales data Object BUS1116 (Profit Center Group) .Method Create Change Profit Center Create Profit Center Replicate entire work breakdown structure (ALE) Send Reply for Plant's Required Quantities Insert/Delete employee time overviews Quality data and sending of certificate reference QM: Quality Certificate Replication of QM Code Groups/Catalogs Replication of QM Master Inspection (ALE) Replication of QM inspection methods Information about IDocs and their application documents Information about the reset system BAPI: Create or Change a Redemption Factor
.Method AddNode Object BUS1116 (Profit Center Group) .
Info in Table (w/ Cost Assignment) EHS: Saving Replicated Reports Confirmation request in CC1 Confirmation request in CC2 Confirmation request in CC2 Confirmation request in CC4 Confirmation request in CC5
. Info in Table (w/o Account Assignment) Insert employee remuneration info (PTMgrExtRemunSpec) Insert External EE Remun.REDEMPTIONFACTORS_CREATE01 REDEMPTIONFACTORS_GETDETAIL01
BAPI: Create Redemption Factor Header + Factors BAPI: Read Redemption Factors for a Securities ID
REDEMPTIONSCHEDSET_ADDSCHEDU01 Create Redemption Schedules for Redemption Schedule Sets REDEMPTIONSCHEDSET_CREATE01 REDEMPTIONSCHEDSET_GETDETAIL01 REDEMPTIONSCHEDSET_GETLIST01 Create Redemption Schedule Sets Read Redemption Schedules for Redemption Schedule Sets Read Header Data for Redemption Schedule Sets
REDEMPTIONSET_CHANGESCHEDULE01 Change Repayment Schedule Data REFSETOFOPERATIONS_CREATE01 REMUNREQUESTLIST_GETLIST01 REMURQSLIST_CHANGE01 REMURQSLIST_CREATE_CBD01 REMURQSLIST_CREATE_CBD02 REMURQSLIST_CREATE_REMU01 REMURQSLIST_CREATE_REMU02 REMURQSLIST_CREATE_SETT01 REMURQSLIST_CREATE_SETT02 REMURQSLIST_RELEASE01 REMURQSLIST_RELEASE02 REM_SPEC01 REM_SPEC_WITH_ACTIVITY01 REM_SPEC_WITH_COST01 REPMAS01 REQUI1 REQUI2 REQUI3 REQUI4 REQUI5 Creation of a reference operation set Determine Documents (RemunRequestList) Agency Business: Change Invoice List Documents BAPI Create from posting list (invoice list) Create from posting list (invoice list) Create from shipping document (invoice list) Create from shipping document (invoice list) Create from payment document (invoice list) Create from payment document (invoice list) Release to Accounting (Invoice List) Release to Accounting (Invoice List) Insert Ext. EE Remun.
RESOURCECO01 ROUTING_CREATE01 RPLMAS01 RPLMAS02 RPMINTF1 RSINFO RSREQUST RSSEND SALESORDER_CONFIRMDELIVERY01 SALESORDER_CREATEFROMDAT201 SALESORDER_CREATEFROMDAT202 SAPRDI01 SAPRDI02 SCERTKB SDPAID01 SDPIID01 SDPIOD01 SERDAT01 SERVICENOTIFICATION_CREATEFR01 SETTLEMENTREQUSTLIST_GETLIST01 SETTRQSLIST_CHANGE01 SETTRQSLIST_CHANGE02 SETTRQSLIST_CLOSE01 SETTRQSLIST_CREATE01 SETTRQSLIST_CREATE02 SETTRQSLIST_RELEASE01 SETTRQSLIST_RELEASE02
Replicate Individual CO Resources (ALE) Creation of a routing Create and change replenishment master data Create and Change Replenishment Master Data RPM FI Interface Info IDoc Data request to the source system Data transfer from the source system (template) Delivery Confirmation (SalesOrder) Sales order: Create Sales Order Sales order: Create Sales Order SAPscript Raw Data Interface IDOC Type SAPscript Raw Data Interface IDOC Type Knowledge base for configurator Shipping element data confirmation to customer delivery Picking data confirmation to customer delivery Picking notification to subsystem: Control data serialization Create service notification Determine Documents (SettlementRequstList) Agency Business: Change Settlement Request List BAPI Agency Business: Change Settlement Request List BAPI Agency Business: BAP(SettlementRequstList) Agency Business: Create Settlement Request List BAPI Agency Business: Create Settlement Request List BAPI Release to Accounting (SettlementRequstList) Release to Accounting (SettlementRequstList)
SFADCH01 SFADDE01 SFADOR01 SFADPSA01 SFAMAT01 SHIPMENT_CHANGE01 SHIPMENT_CREATEFROMDATA01 SHIPMENT_CREATEFROMDATA02 SHPMNT01 SHPMNT02 SHPMNT03 SHPMNT04 SHPMNT05 SHP_IBDLV_CHANGE01 SHP_IBDLV_CONFIRM_DECENTRAL01 SHP_IBDLV_CONFIRM_DECENTRAL02 SHP_IBDLV_SAVE_REPLICA01 SHP_IBDLV_SAVE_REPLICA02 SHP_OBDLV_CHANGE01 SHP_OBDLV_CONFIRM_DECENTRAL01 SHP_OBDLV_CONFIRM_DECENTRAL02 SHP_OBDLV_CONFIRM_DECENTRAL03 SHP_OBDLV_SAVE_REPLICA01 SHP_OBDLV_SAVE_REPLICA02 SHP_OBDLV_SPLIT_DECENTRAL01 SINGLEREMUNREQUEST_GETLIST01 SINGLEREMUNRQS_CANCEL01
SFA download salesorder (change pointers) SFA Download Debitor SFA Download Salesorder BAPI Partner Sales Activity Receiver SFA MATERIAL DOWNLOAD IDOC Change Shipment Create Shipment Create Shipment Shipment Shipment Shipment Transport Shipment Change inbound delivery BAPI Confirmation(InboundDelivery) BAPI Confirmation(InboundDelivery) BAPI Function Module for Replication of Inbound Deliveries BAPI Function Module for Replication of Inbound Deliveries BAPI for Change to Outbound Delivery BAPI Verification (OutboundDelivery) BAPI Verification (OutboundDelivery) BAPI Verification (OutboundDelivery) BAPI Function Module for Replication of Outbound Deliveries BAPI Function Module for Replication of Outbound Deliveries BAPI delivery split (outbound delivery) Determine Documents (SingleRemunRequest) Agency Business: Cancel Vendor Billing Documents BAPI
billing document General info structure distribution Source List Service master record with texts STTMAT: Material variants EHS: Saving Replicated Specifications CA-EDI: Transport of IDoc types Dummy IDoc type for synchronous communication Transfer from partner profiles CA-EDI: Transport of IDoc record types IDoc Interface: Transport IDoc record types CA-EDI: Transfer from status records Units of measurement
.Sales order SIS .SINGLEREMUNRQS_CHANGE01 SINGLEREMUNRQS_CREATE01 SINGLEREMUNRQS_RELEASE01 SINGLEREMUNRQS_RELEASE02 SINGLESETTLEMENTREQS_GETLIST01 SINGLESETTRQS_CANCEL01 SINGLESETTRQS_CHANGE01 SINGLESETTRQS_CHANGE02 SINGLESETTRQS_CREATE01 SINGLESETTRQS_CREATE02 SINGLESETTRQS_RELEASE01 SINGLESETTRQS_RELEASE02 SISCSO01 SISDEL01 SISINV01 SOPGEN01 SRCLST01 SRVMAS01 STTMAT01 SUBMAS01 SYIDOC01 SYNCHRON SYPART01 SYRECD01 SYRECD02 SYSTAT01 T006_01
Agency Business: Change Vendor Billing Documents BAPI Agency Business: Generate Vendor Billing Documents BAPI Release to Accounting (Vendor Billing Documents) Release to Accounting (Vendor Billing Documents) Determine Documents (SingleSettlementReqs) Agency Business: BAPI Cancel Single Settlement Requests Agency Business: BAPI Change Single Settlement Requests Agency Business: BAPI Change Single Settlement Requests Agency Business: Create Bapi Single Requests Agency Business: Create Bapi Single Requests Release Accounting (SingleSettlementReqs) Release Accounting (SingleSettlementReqs) SIS .delivery SIS .
and CO Selection via variant from external system Dispatch of delivery documents to shipping planning system Dispatch of location master data to transport planning syst.TCURC_01 TCURR_01 TEMPLATECO_CREATEFROMDATA01 TEMPLATECO_DELETE01 TIMESHEETCPRCONNECT_TRANSCPR01
Currency Codes Exchange rates CreateFromData for Business Object TemplateCO Delete for Business Object TemplateCO Transfer CATS II Data by cProjects
TIMESHEETHRCONNECTOR_DATATRA01 Transfer of CATS II Data into HR TIMESHEETLOCOCONNECT_TRACO01 TIMESHEETLOCOCONNECT_TRAPM01 TIMESHEETLOCOCONNECT_TRAPS01 TPSDLR01 TPSDLS01 TPSLOC01 TPSSHT01 TRADINGCONTRACT01 TRADINGCONTRACT_CHANGE01 TRPL_PNR_IDOC TRXSTA02 TXTRAW01 TXTRAW02 UNIMA2 UNIT2 UNIT3 UNIT4 UPLOAD UPSMAS01 UPSRCP01 USERACTGROUPSASSIGN01 Transfer of CATS II Data into PS. PM. and CO Transfer of CATS II Data into PS. PM. PM. and CO Transfer of CATS II Data into PS. Dispatch of planned shipments from transport planning system Trading Contract: Create from Template Data Trading Contract: Change Template Data IDoc Data Structure of Generic PNR (TRPL_PNR) Tracking Event Message Transfer free text to SAPoffice format 'RAW' Transfer free text to SAPoffice format 'RAW' Alternative units of measure with acquisition of materials Units in CC2 Units in CC3 Units in CC4 Configuration transceiver for upload MASTER : ALE Distribution Unit RECEIPT : ALE Distribution Unit User: Change entire activity group assignment
USERACTGROUPSDELETE01 USERCHANGE01 USERCLONE01 USERCLONE02 USERCLONE03 USERCLONE04 USERCREATE01 USERDELETE01 USERLOCK01 USERPROFILESASSIGN01 USERPROFILESDELETE01 USERRESPONSE01 USERUNLOCK01 USER_WPPERSDATASAVE01 VALPROJECTSTOCK_PRICECHANGE01 VALSALESORDSTOCK_PRICECHANGE01 VALSCALE01 VCHARVAL01 VCUI_DELETE01 VCUI_EXISTENCECHECK01 VCUI_SAVEM01 VCUI_SAVEM02 VENDCBDLIST_CHANGE01 VENDCBDLIST_CREATE01 VENDCBDLIST_CREATE02 VENDCBDLIST_RELEASE01 VENDCBDLIST_RELEASE02
User: Delete entire activity group assignment Change User Create user with template in another system Create user with template in another system Create User with Template in Another System Create User with Template in Another System BAPI to Create a User BAPI to Delete a User Lock User User: Assign profiles User: Delete All Profile Assignments Users: Confirmation to Central System Unlock user Writing the WP Personalization Data for a User Material Price Change Material Price Change Maintain Value and Quota scale maintain vendor characteristic values BAPI: Delete Interface Design BAPI: Checks Whether Interface Design Exists Create or Change Interface Design Create or Change Interface Design Agency Business: Change Posting Lists BAPI Agency business: Generate Bapi posting lists Agency business: Generate Bapi posting lists Agency Business: BAPI Release Posting Lists Document to FI Agency Business: BAPI Release Posting Lists Document to FI
99A) Assortment List: Material Data: R/3 Enterprise Release Change Availability Period of a WFM Resource Order receipt IS-R Store order IDoc (inc. 4.VENDTRIGGEREDCBDLIST_GETLIST01 VFNMAS01 VFNMAS02 VTAMAS01 VTAMAS02 VTMMAS01 VTMMAS02 WALNOT01 WALREQ01 WBBDLD01 WBBDLD02 WBBDLD03 WBBDLD04 WFRESOURCE_CHANGEAVAILABILIT01 WGSREQ01 WGSREQ02 WMBIID01 WMCAID01 WMERCAT01 WMINID01 WMIVID01 WMMBID01 WMMBID02 WMPHID01 WMRRID01 WMSUID01 WMTCID01
Agency Business: BAPI Determine Posting List Detailed Data Master Variant Function Master Variant Function + E1UPSLINK Master variants table Master Variant Table + E1UPSLINK
Master maintenance table contents Master Maintenance for Table Contents + E1UPSLINK Allocation: Allocation table notification Allocation: Report requested quantities Assortment list: Material data Assortment list: material data (Rel.0) Assortment lists: Material data (Rel. condition segment) Block Storage Bins Reversal/Reversal request for transfer order Merchandise Category and associated data IDoc Information text for link to subsystems Enter count results Goods movements for mobile data entry Stock movements from ext. systems Pick HU (Handling Unit) Release reference number Move storage unit Confirm transfer order
. interface SRS/POS POS Interface: Inbound processing cashier data for POS stats POS interface: Upload day-end closing POS POS interface: Upload sales data (compressed) POS interface: Upload goods movements POS interface: Upload/Download EAN assignments POS interface: Upload/Download person data POS interface: Upload/Download article master POS interface: material and condition (inbound and outb.WMTCID02 WMTCID03 WMTOID01 WMTOID02 WMTRID01 WORKC2 WORKC3 WORKC4 WORKSCHED_WITH_COST01 WPDBBY01 WPDCUR01 WPDNAC01 WPDREB01 WPDSET01 WPDTAX01 WPDWGR01 WPUBON01 WPUERR01 WPUFIB01 WPUKSR01 WPUTAB01 WPUUMS01 WPUWBW01 WP_EAN01 WP_PER01 WP_PLU01 WP_PLU02
Confirm transfer order Confirm TO Transfer order Send pick HU Transfer requirement Workcenters in CC2 Work centers in CC3 Workcenters in CC4 Insert Operative Planned Working Time (With Cost Assignment) POS outbound: bonus buy conditions POS interface: Download exchange rates POS interface: Download products POS interface: Download special offer discounts POS interface: Download set assignments POS interface: Download tax rates POS interface: Download material group master POS interface: Upload sales docs (trnsctns). non-aggregated POS interface: Upload messages SRS/POS/SCS POS interface: Upload Fin.
2. count data inbound Distribution of material groups
The presentation which has been made here of the use of IDocs in a SAP R/3 environment was only a quick view of the range of given possibilities. some transactions enabling the testing and the monitoring of IDocs will be listed. fastest and most effective way to set up interfaces between SAP R/3 systems. Then.: phy. docs outbound.: phy.WRMA_REV_DATA WRMA_REV_REQUEST WTADDI01 WVINVE01 WVINVE02 WVINVE03 W_WGRP01
RMA revaluation data from BW Data request for revaluation in R/3 system Additionals Store phy.: phy. docs outbound. Indeed. the customizing of an outbound interface will be detailed.inv.com/fr/2005/begin%5Fin%5Fabap4/
. count data inbound Store phy.
Using IDocs is the simplest.inv. docs outbound. count data inbound Store phy.inv. the building of an ABAP interface program will be explained.supinfo-projects. And the almost infinite number of combinations which represents the interoperatibility with third-party EDI systems are even not taken into account. After a presentation of the structure of an IDoc interface in a SAP R/3 system.inv.inv. conversions at customizing level and BADIs. there燼re many ways of interacting between the SAP R/3 system and IDocs. A knowledge of a SAP R/3 system http://www. like TIBCO for example.inv. Last. Some prerequisites are needed before reading the following : 1. and a sequence of further customizing will be given. among them there are change pointers.com/fr/2005/begin%5Fsap%5Fabap/ A knowledge of the ABAP programming language http://www.supinfo-projects.