|
Functionality
This BAPI is used to create warranty claims (Business Object BUS2222).An entitlement to warranty services is determined and documented via thewarranty claim.
A warranty claim header, several claim versions and the appropriateitems can be created with the BAPI. The items are assigned to theversions by numbering the versions (handle) and then entering the handlein the item field HANDLE_VERSION.
Long texts, measurement data, and price information are also assigned tothe header, version or item using a handle.
When you create a claim, you must enter one of the claim types inCustomizing. You can also enter a claim number in accordance with thenumber range of the claim type.
You cannot change existing claims with this BAPI. You should alwaystransfer header data and data for at least one version.
The function modules SAVE_TEXT, COMMIT_TEXT (long text),MEASUREM_DOCUM_RFC_SINGLE_001, MEASUREM_DIALOG_UPDATE (measurementdocuments), RV_MESSAGES_UPDATE (message determination) of otherdevelopment classes are called from this BAPI.
Customer-specific data can be transferred using table EXTENSIONIN.Specific data assignment is carried out using the BAdI WTY_BAPI_CREATE.
The BAPI does not contain a COMMIT-WORK command and buffers the data.
After the COMMIT-WORK command has been triggered, the temporary buffershould be deleted using the function module WTY12_REFRESH_BUFFER_RFC. Description
After the claim has been created, the claim number is returned in theparameter CLAIM. If the BAPI was called in simulation mode, no validclaim number is returned. Description
If this BAPI is called in simulation mode, the claim data that istransferred and determined is still in the data buffer of theappropriate function groups and classes. A GUID (RAW, 16) is generatedfor the claim header that is converted to CHAR and returned with theseparameters. This GUID can then be used for reading the temporary databuffer (for example, as in the BAPI BAPI_WARRANTYCLAIM_SET_ACTION). Description
The header data of a warranty claim are transferred using the importparameter CLAIM_HEADER. The fields CLAIM_TYPE and HANDLE have to befilled. You can enter any value in field HANDLE. However, each HANDLEmay only occur once per claim. If data is transferred in relation tothe header (for example, long text), the same value has to be enteredin the field REF_HANDLE.
The field CLAIM can contain a claim number if an external number rangeinterval is assigned to the claim type used.
All other fields are optional.
The fields ACTION, CLAIM_NOT_EXIST and ACTION_NOT_ALLOWED are not usedin this BAPI. These fields are onyl used in BAPIBAPI_WARRANTYCLAIM_SET_ACTION. Description
If the value "X" is transferred in field SIMULATE, the program forcreating warranty claims is run through, but no update function modulesare called. Furthermore, no claim number is taken from the appropriatenumber range. If a COMMIT WORK command is then called in simulation,the claim is not saved to the database. Description
The table CLAIM_ITEM contains item data for the claim. More than oneversion can be created per claim. More than one item can be created perversion.
The fields HANDLE and HANDLE_VERSION have to have an entry in them.Like the header HANDLE, you can enter any HANDLE but it must be uniquein the claim. You can use the HANDLE to create a relationship betweenthe long texts, price information (item prices) and the item.Relationships between items (predecessor/successor item) are created byentering the HANDLE in table POSITION_REL.
The field HANDLE_VERSION must contain the value of the handle of theversion under which the item is to be created.
The item number in field ITEM_NO does not have to have an entry in it.If no item number is transferred, it is assigned by the program (inascending order).
All other fields are optional.
Description
You can create measurement documents and thus transfer measuring pointsfor the warranty object.
If you want to do this, the fields REF_HANDLE, MEAS_POINT andRECORDED_VALUE in this BAPI have to have an entry in them. The handleof a version or an item has to be in field REF_HANDLE.
A relationship with the appropriate measurement document is thencreated in the claim. The measurement reading is stored in themeasurement document. Description
This table serves to transfer price conditions and surcharge/discountconditions with values. Value range
Required fields are REF_HANDLE, COND_TYPE and COND_AMOUNT. The fieldREF_HANDLE contains the HANDLE for a version or and item. If the tableentry has been assigned to an item, the condition type (COND_TYPE) mustbe contained in the pricing procedure of the claim type and be definedas an item condition. If the table entry has been assigned to aversion, the condition type (COND_TYPE) has to be contained in thepricing procedure of the claim type and be defined as a headercondition. The field COND_AMOUNT contains the condition amount. Description
You can use this table to transfer long texts for the claim i.e. longtexts for the claim header, claim versions and claim items.
Required fields are REF_HANDLE (handle for claim header, claim versionor claim item) and the language LANGU. Description
The table CLAIM_VERSION contains version data for the claim. More thanone version can be created per claim. The fields HANDLE and CATEGORYhave to have an entry in them. Like the header HANDLE, the HANDLE canbe freely chosen, but has to be unique in the claim. You can use theHNADLE to create a relationship between items, long texts, measurementdata and pricing information (version prices) and the version.Relationships between versions (predecessor/successor versions) arecreated by entering the HANDLE in table VERSION_REL.
The version number in field VERSION does not have to have an entry init. If no version number is transferred, one is assigned by the program(in ascending order).
All other fields are optional. Description
Table containing the values of customer-specific fields.
The customer must also implement BAdI WTY_BAPI_CREATE if he/she wantsto make assignments in processing. Description
Table for transferring the predecessor/successor relationships betweenitems. Description
Table containing the messages that have occurred during processing(error/warning/information/success). Description
Table for transferring predecessor/successor relationships betweenversions. |