Warranty Processing Pre Credit ConfigGuide

Warranty Processing_Pre Credit_ConfigGuide
Warranty Processing
Configuration Guide
Page 2 of 70
Contents
Warranty Processing: Configuration Guide ...................................................................................5 1 Purpose........................................................................................................................................ 5 2 Preparation.................................................................................................................................. 5 2.1 Prerequisites......................................................................................................................... 5 2.1.1 Building Blocks................................................................................................................ 5 3 Configuration................................................................................................................................ 5 3.1 QM Standard Setting............................................................................................................. 5 3.1.1 Maintaining QM Standard Setting Catalogs....................................................................5 3.1.2 Maintaining QM Standard Setting Quality Notifications...................................................6 3.2 Manual Step ......................................................................................................................... 7 3.2.1 Creating Function Group ................................................................................................ 7 3.2.2 Changing Function Group .............................................................................................. 8 3.2.3 Defining the Table YWTY_DM......................................................................................12 3.2.4 Defining Generating Table Maintenance Dialog YWTY_DM.........................................17 3.2.5 Creating Transaction Code YWTY_DM........................................................................18 3.2.6 Creating Message Class .............................................................................................. 21 3.2.7 Business Add-Ins: Enhancement of Document Flow....................................................22 3.2.8 Business Add-Ins: Data Checking and Changing for Inbound IDocs............................23 3.2.9 Business Add-Ins: Data Checking and Changing for Outbound IDocs.........................24 3.2.10 Creating Function Model: Good Receipt of Return Parts into Q-Stock.......................25 3.2.11 Creating Function Model: Rel. Version IC for sending................................................38 3.3 EDI Communication General Settings.................................................................................42 3.3.1 Partner Profile, Only Basic Data...................................................................................42 3.3.2 Partner Profile Inbox..................................................................................................... 45 3.3.3 Maintaining a tRFC Port................................................................................................ 46 3.3.4 Maintaining a File Port.................................................................................................. 47 3.3.5 Activating IDoc Inbound................................................................................................ 49 3.4 Creating Claim Type YA02 ................................................................................................. 50 3.5 Creating Claim Type YA01 ................................................................................................. 53 3.6 Creating Notification Type................................................................................................... 53 3.7 Defining Warranty Claim Groups......................................................................................... 54 3.8 Defining Status for Parts to Be Returned.............................................................................55 3.9 Defining Message Type....................................................................................................... 56 3.10 Defining Control Data........................................................................................................ 57 3.10.1 Defining Actions.......................................................................................................... 57
Page 3 of 70

3.10.2 Defining Action Controls............................................................................................. 61 3.10.3 Assigning Function Codes to Action Codes................................................................64 3.10.4 Defining Copy Procedure............................................................................................65 3.10.5 Assigning Copy Procedure to Claim Type..................................................................65 3.11 Layout Settings.................................................................................................................. 66 3.11.1 Defining Pushbutton Profile......................................................................................... 66 3.12 Manual Step...................................................................................................................... 70 3.12.1 Maintaining Document Type Determination for Warranty...........................................70
Page 4 of 70
Warranty Processing: Configuration Guide 1 Purpose

This configuration guide provides the information you need to set up the configuration of this building block manually. If you do not want to configure manually and prefer an automated installation process using BC Sets and other tools, use the Best Practices Installation Assistant.
2 Preparation
2.1 Prerequisites
2.1.1 Building Blocks
Before you start installing this building block, the installation of the following building blocks must have been completed: Building Block Baseline Project for Automotive A01 (Sales) A05 (Sales) Description In Sales client Automotive Basic Settings Master Data for Automotive
3 Configuration
3.1 QM Standard Setting
3.1.1 Use
The purpose of this activity is to copy entries for QM standard settings for catalogs from client 000 to the installation client.
Maintaining QM Standard Setting Catalogs
Procedure
Page 5 of 70

1. Access the activity using one of the following navigation options: Transaction Code QCCK
2. Confirm the Do you want to copy customizing to your client? dialog box with Yes.
3. The system displays the result. 4. Choose Back.
Result
You have copied the QM Standard Settings for Catalogues from client 000 to your installation client.
3.1.2 Use
Maintaining QM Standard Setting Quality Notifications
The purpose of this activity is to copy entries for QM Standard Settings for Quality Notifications from client 000 to the installation client.
Procedure
Page 6 of 70

1. Access the activity using one of the following navigation options: Transaction Code QCCM
2. Confirm the Do you want to copy customizing to your client? Dialog box with Yes.
3. The system displays the result. 4. Choose Back.
Result
You have copied the QM Standard Settings for Quality Notifications from client 000 to your installation client.
3.2 Manual Step

3.2.1 Creating Function Group Procedure
1. Access the activity using one of the following navigation options: SAP Menu Transaction Code Tools ABAP Workbench Development Function Builder SE37
2. On the Function Builder: Initial Screen choose from the menu: Goto Function Group Create Group. 3. In the Create Function Group dialog box, make the following entries: Field Function Group Short Text User action and values Y_WTY_AT Warranty Development
Page 7 of 70
4. Choose Save. 5. In the Create Object Directory Entry dialog box, choose Local Object. 6. Repeat steps 2 5 to create function group Y_WTY_TABLE. Make the following entries: Field Function Group Short Text User action and values Y_WTY_TABLE Extended Table Maintenance (Generated)
7. Go Back to the SAP Easy Access screen.
Result
The Function Groups are created.
3.2.2
Changing Function Group
Procedure
1. Access the activity using one of the following navigation options:
Page 8 of 70

SAP Menu Transaction Code Tools ABAP Workbench Development Function Builder SE37
2. On the Function Builder: Initial Screen, choose from the menu: Goto Function Group Change Group. 3. In the Change Function Group dialog box, make the following entries: Field Function Group 4. Choose Continue. 5. On the Change Function Group dialog box, choose Main program. 6. On the following screen, choose Display <-> Change. 7. On the ABAP Editor, check the following code:
******************************************************************* * System-defined Include-files. * ******************************************************************* INCLUDE LY_WTY_ATTOP. " Global Data INCLUDE LY_WTY_ATUXX. " Function Modules ******************************************************************* * User-defined Include-files (if necessary). * ******************************************************************* * INCLUDE LY_WTY_ATF... " Subprograms * INCLUDE LY_WTY_ATO... " PBO-Modules * INCLUDE LY_WTY_ATI... " PAI-Modules
User action and values Y_WTY_AT
Page 9 of 70
8. Choose Save. 9. Choose Activate. 10. On the Inactivate Object for user XXXXXXXX View, Local Objects tab page, Field name Object name Object name 11. Choose Continue. 12. Choose Back (F3). 13. If the Change Function Group dialog box appears, choose Cancel. 14. Repeat steps 2 7 to change the function group Y_WTY_TABLE. On the ABAP Editor check the following code:
******************************************************************* * System-defined Include-files. * ******************************************************************* INCLUDE LY_WTY_TABLETOP. " Global Data INCLUDE LY_WTY_TABLEUXX. " Function Modules
Description SAPLY_WTY_AT LY_WTY_ATTOP
User action and values Selected Selected
Note
Page 10 of 70
Page 11 of 70
15. Choose Save. 16. Choose Activate. 17. On the Inactivate Object for user XXXXXXXX View, Local Objects tab page, make the following entries: Field name Object name Object name 18. Choose Continue. 19. Choose Back. If the Change Function Group dialog box appears, choose Cancel. 20. Go Back to the SAP Easy Access screen. Description SAPLY_WTY_TABLE LY_WTY_TABLETOP User action and values Selected Selected Note
3.2.3 Use
Defining the Table YWTY_DM
The purpose of this activity is to define the table.
Procedure
1. Access the activity using one of the following navigation options: SAP Menu Transaction Code Tools ABAP Workbench Development ABAP Dictionary SE11
Page 12 of 70

2. On the ABAP Dictionary: Initial Screen, enter the following data: Field name Database Table 3. Choose Create. Description Database Table Name User action and values YWTY_DM Note
4. On the Dictionary: Maintain Table screen, make the following entries: Field name Short Text Description User action and values Document Type Determination for Warranty A Display / Maintenance Allowed Application table Select from the dropdown list Note
Delivery Class Data Browser / Table View Maintenance 5. Choose the tab Fields.
6. On the screen Dictionary: Maintain Table, make the following entries:
Page 13 of 70

Field Name Entry 1 Entry 2 Entry 3 Field MANDT RELTY CLMGRP Key Selected Selected Selected Initial Values Selected Selected Selected Data element MANDT WTY_RELTY WTY_CLMGRP
Page 14 of 70

Field Name Entry 4 Field CLMTY Key Blank Initial Values Blank Data element WTY_CLMTY
7. Choose ENTER to confirm your entries. 8. Select the CLMGRP row. 9. Choose Foreign Keys .
10. On the screen Create Foreign Key YWTY DM-CLMGRP, in the field Check table enter CWTY006. 11. Choose Enter to confirm your entries, and confirm the dialog box with Yes.
Page 15 of 70
12. Select the radio button Key fields/candidates, and fill the Cardinality with 1:1. 13. Choose Copy to confirm your entries. 14. On the Dictionary: Maintain Table screen, choose Technical Settings. 15. Confirm the dialog box with Yes and save as local object. 16. On the screen Dictionary: Maintain Technical Settings, enter the following entries: Field name Data class Size category 17. Choose Save, and go Back. 18. Choose Activate to activate the table. 19. Choose No if warning message appears.. 20. Choose Back to the SAP Easy Access screen. Description User action and values APPL0 0 Note
Result
Table YWTY_DM has been defined.
Page 16 of 70
3.2.4 Use
Defining Generating Table Maintenance Dialog YWTY_DM
The purpose of this activity is to define the generate table maintenance dialog.
Procedure
1. Access the activity using one of the following navigation options: SAP Menu Transaction Code Tools ABAP Workbench Development Other Tools General Table Maintenance Dialog SE54
2. On the Generate Table Maintenance Dialog: Initial Table/View Screen, make the following entries: Field name Generated Objects Table / View 3. Choose Create/change. 4. Confirm the dialog box with Yes. 5. On the Generate Table Maintenance Dialog: Generate Environment screen, make the following entries: Field name User action and values AC Y_WTY_TABLE One step 1 Set the indicator Note Description Check the Generated Objects User action and values Set indicator YWTY_DM Note
Technical Dialog Details View Authorization Group Function Group Maintenance Type Maintenance Screen No: Overview Screen Recording routine AM: User Control
Maintenance Screens View
Dialog Data Transport Details no, or user, recording routine Set the indicator
Page 17 of 70
6. Choose Create. 7. In the Create Object Directory Entry dialog box, choose Local Object. 8. Choose Back twice to the SAP Easy Access screen.
3.2.5 Use
Creating Transaction Code YWTY_DM
The purpose of this activity is to create transaction code YWTY_DM.
Procedure
1. Access the activity using one of the following navigation options: SAP Menu Transaction Code Tools ABAP Workbench Development Other Tools Transactions SE93
Page 18 of 70

2. On the Maintain Transaction screen, make the following entries: Field Transaction Code 3. Choose Create. 4. In the Creation Transaction dialog box, make the following entries: Field Transaction Code Short Text Start Object Transaction with parameters (parameter transaction) 5. Choose Continue (Enter). 6. On the Create Parameter Transaction screen, make the following entries: Field Default values for Transaction Skip initial screen Classification Inherit GUI attributes Default Values Name of screen field value Name of screen field value UPDATE X VIEWNAME YWTY_DM Set indicator SM30 Set indicator User action and values Set the indicator User action and values YWTY_DM Warranty Table Maintenance User action and values YWTY_DM
Page 19 of 70
7. Choose Save. 8. In the Create Object Directory Entry dialog box, choose Local Object. 9. Go back to the SAP Easy Access menu.
Page 20 of 70
3.2.6 Use
Creating Message Class
The purpose of this activity is to create message class YEAT.
Procedure
1. Access the activity using one of the following navigation options: SAP Menu Transaction Code Tools ABAP Workbench Development Programming Environment Messages SE91
2. On the Message Maintenance Initial Screen, make the following entries: Field Message Class User action and values YEAT
3. Choose Create. 4. On the Attributes tab page, make the following entries: Field Short Text User action and values Automotive - Warranty
Page 21 of 70

5. Choose Save. 6. In the Create Object Directory Entry dialog box, choose Local Object 7. Select the Messages tab page, make the following entries: Message Field 001 009 010 User action and values Material document & created when claim is saved Program run O.K. Program run not O.K.
8. Choose Save. 9. Go Back to the SAP Easy Access screen.
Result
Message class YEAT is created.
3.2.7
Business Add-Ins: Enhancement of Document Flow
Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu OWTY Warranty Claim Processing Business Add-Ins Processing of Warranty Claims BADI: Enhancement of Document Flow
2. Choose Create. 3. In the Business Add-In Builder: Create Implementation dialog box, make the following entries:
Page 22 of 70

Field Implementation Name 4. Choose Continue. 5. In the following screen, make the following entries; Field Implementation Short Text 6. Choose Save. 7. In the Create Object Directory Entry dialog box, choose Local Object. In the Information Window choose Continue. 8. On the Select or Create Enhancement Implementation screen, choose Create Enhancement Implementation and make the following entries: Field Enhancement Implementation Short Text 9. Choose Save. 10. In the Create Object Directory Entry dialog box, choose Local Object. 11. On the Select or Create Enhancement Implementation screen, select Y_WTY_DOCU_ADD and choose Enter. 12. Go to the Interface tab page, double click the method ADD_DOCUMENT. 13. On the ABAP Editor, delete all of old source codes. 14. Load the source code from ADD_DOCUMENT.txt under \MISC\ A20 folder on the DVD. 15. Choose Save and then Activate. 16. On the appearing dialog box, choose continue. 17. Choose Back. 18. Double click the other method DOCUMENT_DISPLAY. 19. On the ABAP Editor, delete all of old source codes. 20. Load the source code from DOCUMENT_DISPLAY.txt under \MISC\ A20 folder on the DVD. 21. Choose Save and Activate. 22. On the appearing dialog box, choose Continue. 23. Choose Back. 24. On the Business Add-In Builder: Change Implementation Y_WTY_DOCU_ADD screen, choose Activate. 25. Go Back to the IMG menu. User action and values Y_WTY_DOCU_ADD BP for Automotive User action and values BP for Automotive User action and values Y_WTY_DOCU_ADD
3.2.8
Business Add-Ins: Data Checking and Changing for Inbound IDocs
Page 23 of 70
Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu OWTY Warranty Claim Processing Business Add-Ins External Creation of Warranty Claims Data Check and Change for Inbound Idocs User action and values Y_WTY_IDOC_IN
2. In the Business Add-In Builder: Create Implementation dialog box, make the following entries: Field Implementation Name 3. Choose Continue (Enter). 4. On the following screen, make the following entries; Field Implementation Short Text 5. Choose Save. 6. In the Create Object Directory Entry dialog box, choose Local Object. 7. On the Interface tab page, double click the method CHECK_IDOC. 8. On the ABAP Editor, delete all of old source codes. 9. Load the source code from CHECK_IDOC.txt under \MISC\ A20 folder on the DVD. 10. Choose Save and Activate. 11. On the appearing dialog box, choose Continue. 12. Choose Back. 13. Double click method INTERPRET_ADDITIONAL_SEGMENT. 14. Choose Activate, and on the appearing dialog box, choose Continue. 15. Choose Back. 16. Repeat step 12-14 to activate method INTERPRET_IDOC, CHANGE_EXPORT_PARAMETERS and CHECK_PARTNER. 17. On the Business Add-In Builder: Change Implementation Y_WTY_IDOC_IN screen, choose Activate. 18. Go back to the IMG menu. User action and values Change Inbound Warranty Idoc
3.2.9
Business Add-Ins: Data Checking and Changing for Outbound IDocs
Procedure
1. Access the activity using one of the following navigation options: Transaction Code OWTY
Page 24 of 70

IMG Menu Warranty Claim Processing Business Add-Ins External Creation of Warranty Claims Data Check and Change for Outbound Idocs User action and values Y_WTY_IDOC_OUT
2. In the Business Add-In Builder: Create Implementation dialog box, make the following entries: Field Implementation Name 3. Choose Continue (Enter). 4. On the following screen, make the following entries; Field Implementation Short Text 5. Choose Save. 6. In the Create Object Directory Entry dialog box, choose Local Object. 7. On the Interface tab page, double click the method CHANGE_SEGMENT. 8. On the ABAP Editor, delete all of old source codes. 9. Load the source code from CHANGE_SEGMENT.txt under \MISC\ A20 folder on the DVD. 10. Choose Save and then Activate. 11. On the appearing dialog box, choose Continue. 12. Choose Back. 13. On the Business Add-In Builder: Change Implementation Y_WTY_IDOC_OUT screen choose Activate. 14. Go Back to the IMG menu. User action and values Change Outbound Warranty Idoc
3.2.10 Creating Function Model: Good Receipt of Return Parts into Q-Stock Procedure
2. In the Function Builder: Initial Screen dialog box, make the following entry: Field Function Module 3. Choose Create. User action and values Y_WTY04_GR_QSTOCK
Page 25 of 70
4. On the following screen, make the following entries; Field Function Group Short Text User action and values Y_WTY_AT Good Receipt of Return Pats into Q-Stock
5. Choose Enter. 6. On the following screen, select the tab Import, and make the following entries: Parameter Name IT_RCODE IV_RCODE_MAX IV_MODE IV_ACODE Type Spec. TYPE TYPE TYPE TYPE Associated Type WTY_RCODE_TAB SYSUBRC WTY_MODE WTY_ACODE Optional X X X X
Page 26 of 70
7. Select the tab Export, and make the following entries: Parameter Name EV_RETURN_CODE EV_SAVE_DATA Type Spec. TYPE TYPE Associated Type SYSUBRC C Optional
8. Select the tab Changing, and make the following entries: Parameter Name CT_PRELID CS_PNWTYH_DIA CT_PNWTYV_DIA CT_PVWTY_DIA Type Spec. TYPE TYPE TYPE TYPE Associated Type PRWTY_TAB WTY_PNWTYH_DIA WTY_PNWTYV_DIA_TAB WTY_PVWTY_DIA_TAB Optional X X X X
Page 27 of 70
9. Select the tab Source Code 10. On the ABAP Editor, delete all of old source codes. 11. Load the source code from Y_WTY04_GR_QSTOCK.txt under \MISC\ A20 folder on the DVD.
Page 28 of 70
Page 29 of 70
Page 30 of 70
Page 31 of 70
Page 32 of 70
FUNCTION Y_WTY04_GR_QSTOCK. *"---------------------------------------------------------------------*"*"Local Interface: *" IMPORTING *" REFERENCE(IT_RCODE) TYPE WTY_RCODE_TAB OPTIONAL *" REFERENCE(IV_RCODE_MAX) TYPE SYSUBRC OPTIONAL *" REFERENCE(IV_MODE) TYPE WTY_MODE OPTIONAL *" REFERENCE(IV_ACODE) TYPE WTY_ACODE OPTIONAL *" EXPORTING *" REFERENCE(EV_RETURN_CODE) TYPE SYSUBRC *" REFERENCE(EV_SAVE_DATA) TYPE C *" CHANGING *" REFERENCE(CT_PRELID) TYPE PRWTY_TAB OPTIONAL *" REFERENCE(CS_PNWTYH_DIA) TYPE WTY_PNWTYH_DIA OPTIONAL *" REFERENCE(CT_PNWTYV_DIA) TYPE WTY_PNWTYV_DIA_TAB OPTIONAL *" REFERENCE(CT_PVWTY_DIA) TYPE WTY_PVWTY_DIA_TAB OPTIONAL *"---------------------------------------------------------------------* PVWTY TYPES: pwty_pvwty_li TYPE pvwty, pwty_pvwty_li_tab TYPE STANDARD TABLE OF pwty_pvwty_li WITH KEY pvguid pvcnt. CONSTANTS: cv_bus2222(10) TYPE c VALUE 'BUS2222', cv_bus2032(10) TYPE c VALUE 'BUS2032', * Goods mvmt cv_bus2017(10) TYPE c VALUE 'BUS2017'. DATA: ls_pnwtyv TYPE pnwtyv, ls_pvwty TYPE pvwty, lt_pvwty TYPE pwty_pvwty_li_tab, lt_pvwty_dia TYPE wty_pvwty_dia_tab. DATA: lv_version_guid TYPE pvs_guid,
Page 33 of 70

ls_pnwtyv_dia ls_pvwty_dia lv_docno ls_obj_rolea ls_obj_roleb lv_reltype lv_dummy TYPE wty_pnwtyv_dia, TYPE wty_pvwty_dia, TYPE bapivbeln-vbeln, TYPE borident, TYPE borident, TYPE breltyp-reltype, TYPE string.
DATA: wrk_quan LIKE bapi2017_gm_item_create-entry_qnt, mat_doc LIKE mseg-mblnr, mat_year LIKE mseg-mjahr. DATA: s_head_01 TYPE bapi2017_gm_head_01, s_gm_code TYPE bapi2017_gm_code. DATA: BEGIN OF lt_items OCCURS 0. INCLUDE STRUCTURE bapi2017_gm_item_create. DATA: END OF lt_items. DATA: BEGIN OF lt_return OCCURS 0. INCLUDE STRUCTURE bapiret2. DATA: END OF lt_return. DATA: BEGIN OF i_errors OCCURS 0. INCLUDE STRUCTURE hrale_err. DATA: END OF i_errors. IF iv_rcode_max > 0. ev_return_code = 2. EXIT. ENDIF. CALL FUNCTION 'WTY07_CLEAR_DFLMESSAGES' EXPORTING iv_pnguid = cs_pnwtyh_dia-pnguid iv_dflmsg = 'YAGR' iv_versn = ls_pnwtyv_dia-versn. *--- determine items of active IC-version CLEAR ls_pnwtyv. CALL FUNCTION 'WTY03_ITEM_FROM_AC_VERSION_GET' EXPORTING it_pnwtyv_dia = ct_pnwtyv_dia iv_kateg = 'IC' it_pvwty_dia = ct_pvwty_dia IMPORTING es_pnwtyv = ls_pnwtyv et_pvwty = lt_pvwty EXCEPTIONS no_active_version = 1 no_item =2 OTHERS = 3. IF sy-subrc <> 0. ev_return_code = 1. exit. endif. s_gm_code-gm_code = '05'. s_head_01-pstng_date = sy-datum.
Page 34 of 70

s_head_01-doc_date = sy-datum. s_head_01-pr_uname = sy-uname. CONCATENATE 'Claim ' cs_pnwtyh_dia-clmno INTO s_head_01-header_txt separated by space. REFRESH lt_items. * Select those items which have to be returned LOOP AT lt_pvwty into ls_pvwty where RETPA = 1. CLEAR lt_items. wrk_quan = ls_pvwty-quant. lt_items-material = ls_pvwty-matnr. lt_items-plant = cs_pnwtyh_dia-werks. SELECT single maktx FROM MAKT into lt_items-item_text WHERE MATNR = ls_pvwty-matnr AND SPRAS = sy-langu. lt_items-stge_loc = 'Z001'. * YD03 refers to the storage location for return parts. In case the *storage location is not YD03, change the source code above *accordingly. lt_items-move_type = '503'. lt_items-entry_qnt = wrk_quan. lt_items-entry_uom = ls_pvwty-meinh. * ISO-Code CALL FUNCTION 'RH_ALE_MEASURE_CODE_SAP_TO_ISO' EXPORTING measure_sap = ls_pvwty-meinh field_name_sap = 'ERFME' IMPORTING measure_iso = lt_items-entry_uom_iso TABLES error_table = i_errors. lt_items-ref_date = sy-datum. lt_items-move_reas = space. "Grund der Bew. APPEND lt_items. ENDLOOP. REFRESH: lt_return. CLEAR: mat_doc, mat_year. IF NOT lt_items[] IS INITIAL. CALL FUNCTION 'BAPI_GOODSMVT_CREATE' EXPORTING goodsmvt_header = s_head_01 goodsmvt_code = s_gm_code IMPORTING materialdocument = mat_doc matdocumentyear = mat_year TABLES goodsmvt_item = lt_items return = lt_return.
Page 35 of 70
LOOP AT lt_return WHERE type <> 'E' AND type <> 'A'. DELETE lt_return. ENDLOOP.
*--- claim IF lt_return[] IS INITIAL. MOVE cs_pnwtyh_dia-clmno TO ls_obj_rolea-objkey. MOVE cv_bus2222 TO ls_obj_rolea-objtype. *--- Material document. MOVE mat_doc TO ls_obj_roleb-objkey. MOVE cv_bus2017 TO ls_obj_roleb-objtype. * Relationtype MOVE 'VONA' TO lv_reltype. PERFORM document_flow_create USING ls_obj_rolea ls_obj_roleb lv_reltype cs_pnwtyh_dia-pnguid. MESSAGE i001(YA71) WITH mat_doc into lv_dummy. MESSAGE i001(YEAT) WITH mat_doc. Material document & created when claim is saved CALL FUNCTION 'WTY07_MESSAGE_PROCESSING' EXPORTING iv_msgty = sy-msgty iv_msgid = sy-msgid iv_msgno = sy-msgno iv_msgv1 = sy-msgv1 iv_msgv2 = sy-msgv2 iv_msgv3 = sy-msgv3 iv_versn = ls_pnwtyv_dia-versn iv_dflmsg = 'YAGR' iv_pnguid = cs_pnwtyh_dia-pnguid. Change status of Parts to 3 - "Partial delivered" LOOP AT lt_pvwty into ls_pvwty where RETPA = 1. read table CT_PVWTY_DIA into ls_pvwty_dia with key pvguid = ls_pvwty-pvguid. if sy-subrc = 0. ls_pvwty_dia-retpa = 3. modify CT_PVWTY_DIA index sy-tabix from ls_pvwty_dia transporting retpa. endif. ENDLOOP. ev_return_code = 0. ELSE. LOOP AT lt_return. MESSAGE ID lt_return-id TYPE lt_return-type NUMBER lt_return-number WITH lt_return-message_v1 lt_return-message_v2 lt_return-message_v4 lt_return-message_v4. CALL FUNCTION 'WTY07_MESSAGE_PROCESSING' EXPORTING
* * * * * * * * * * * * * *
Page 36 of 70

iv_msgty = sy-msgty iv_msgid = sy-msgid iv_msgno = sy-msgno iv_msgv1 = sy-msgv1 iv_versn = ls_pnwtyv_dia-versn iv_dflmsg = 'YAGR' iv_pnguid = cs_pnwtyh_dia-pnguid. ENDLOOP. ev_return_code = 4. ENDIF. ENDIF. ENDFUNCTION. *&---------------------------------------------------------------------* *& Form document_flow_create *&---------------------------------------------------------------------* * text *----------------------------------------------------------------------* * -->P_LV_OBJ_ROLEA text * -->P_LS_OBJ_ROLEB text * -->P_LV_RELTYPE text *----------------------------------------------------------------------* FORM DOCUMENT_FLOW_CREATE USING CS_OBJ_ROLEA LIKE BORIDENT CS_OBJ_ROLEB LIKE BORIDENT CV_OBJ_RELTYPE LIKE BRELTYP-RELTYPE IV_HEADER_GUID TYPE PVS_GUID. DATA: LV_OWN_LOGICAL_SYSTEM TYPE TBDLS-LOGSYS, LV_MSGTXT TYPE STRING. * get own logical system CALL FUNCTION 'OWN_LOGICAL_SYSTEM_GET' IMPORTING OWN_LOGICAL_SYSTEM = LV_OWN_LOGICAL_SYSTEM EXCEPTIONS OWN_LOGICAL_SYSTEM_NOT_DEFINED = 0. *--- Object A CS_OBJ_ROLEA-LOGSYS = LV_OWN_LOGICAL_SYSTEM. *--- Object B CS_OBJ_ROLEB-LOGSYS = LV_OWN_LOGICAL_SYSTEM. *--- create relation CALL FUNCTION 'WTY07_CLEAR_DFLMESSAGES' EXPORTING IV_MSGID = 'WTY' IV_MSGNO = 114 IV_PNGUID = IV_HEADER_GUID. CALL FUNCTION 'BINARY_RELATION_CREATE' EXPORTING obj_rolea = CS_OBJ_ROLEA obj_roleb = CS_OBJ_ROLEB relationtype = CV_OBJ_RELTYPE EXCEPTIONS
Page 37 of 70

NO_MODEL =1 INTERNAL_ERROR = 2 UNKNOWN =3 OTHERS = 4. * CALL FUNCTION 'BINARY_RELATION_CREATE' * EXPORTING * OBJ_ROLEA = CS_OBJ_ROLEA * OBJ_ROLEB = CS_OBJ_ROLEB * RELATIONTYPE = CV_OBJ_RELTYPE * EXCEPTIONS * NO_MODEL =1 * INTERNAL_ERROR = 2 * UNKNOWN =3 * OTHERS = 4. IF SY-SUBRC <> 0. MESSAGE S114(WTY) INTO LV_MSGTXT. CALL FUNCTION 'WTY07_MESSAGE_PROCESSING' EXPORTING * IT_MESG = IV_MSGTY = SY-MSGTY IV_MSGID = SY-MSGID IV_MSGNO = SY-MSGNO IV_DFLMSG = 'R3' IV_PNGUID = IV_HEADER_GUID. ENDIF. ENDFORM. " document_flow_create
In our solution we use the storage location for returnable parts YD03. If you wish to personalize your solution and change your storage location for returnable parts to another value, ensure you change the value YD03 in the source code below, to your own storage location. lt_items-stge_loc = 'YD03'. 12. Choose Save and Activate. 13. Go Back the SAP Easy Access screen.
3.2.11
Creating Function Model: Rel. Version IC for sending
Procedure
2. On the Function Builder: Initial Screen dialog box, make the following entries:
Page 38 of 70

Field Function Module User action and values Y_WTY04_VER_IC_SEND
3. Choose Create. 4. On the following screen, make the following entries: Field Function Group Short Text User action and values Y_WTY_AT Rel. Version IC for Sending
5. Choose Enter. 6. Select the tab Import, and make the following entries: Parameter Name IT_RCODE IV_RCODE_MAX IV_MODE Type Spec. TYPE TYPE TYPE Associated Type WTY_RCODE_TAB SYSUBRC WTY_MODE Optional X X X
Page 39 of 70
7. Select the tab Export, and make the following entries: Parameter Name EV_RETURN_CODE Type Spec. TYPE Associated Type SYSUBRC Optional
8. Select the tab Changing, and make the following entries: Parameter Name CT_PRELID CS_PNWTYH_DIA CT_PNWTYV_DIA CT_PVWTY_DIA Type Spec. TYPE TYPE TYPE TYPE Associated Type PRWTY_TAB WTY_PNWTYH_DIA WTY_PNWTYV_DIA_TAB WTY_PVWTY_DIA_TAB Optional X X X X
9. Select the tab Source Code. 10. On the ABAP Editor, delete all of old source codes. 11. Load the source code from Y_WTY04_VER_IC_SEND.txt under \MISC\ A20 folder on the DVD.
Page 40 of 70
FUNCTION Y_WTY04_VER_IC_SEND. *"---------------------------------------------------------------------*"*"Local Interface: *" IMPORTING *" REFERENCE(IT_RCODE) TYPE WTY_RCODE_TAB OPTIONAL *" REFERENCE(IV_RCODE_MAX) TYPE SYSUBRC OPTIONAL *" REFERENCE(IV_MODE) TYPE WTY_MODE OPTIONAL
Page 41 of 70

*" EXPORTING *" REFERENCE(EV_RETURN_CODE) TYPE SYSUBRC *" CHANGING *" REFERENCE(CT_PRELID) TYPE PRWTY_TAB OPTIONAL *" REFERENCE(CS_PNWTYH_DIA) TYPE WTY_PNWTYH_DIA OPTIONAL *" REFERENCE(CT_PNWTYV_DIA) TYPE WTY_PNWTYV_DIA_TAB OPTIONAL *" REFERENCE(CT_PVWTY_DIA) TYPE WTY_PVWTY_DIA_TAB OPTIONAL *"---------------------------------------------------------------------IF iv_rcode_max > 0. ev_return_code = 2. EXIT. ENDIF. CALL FUNCTION 'WTY03_VERSION_XX_SEND' EXPORTING it_rcode = it_rcode iv_rcode_max = iv_rcode_max iv_mode = iv_mode iv_kateg = 'IC' IMPORTING ev_return_code = ev_return_code CHANGING cs_pnwtyh_dia = cs_pnwtyh_dia ct_pnwtyv_dia = ct_pnwtyv_dia ct_pvwty_dia = ct_pvwty_dia. ENDFUNCTION. 12. Choose Save and Activate. 13. Go Back to the SAP Easy Access screen.
3.3 EDI Communication General Settings

3.3.1 Use
Partner profiles for EDI communication are created at the supplier side.
Partner Profile, Only Basic Data
Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu WE20 Basis Components Application Link Enabling Modeling and Implementing Business Processes Partner profiles and Time of processing Maintain Partner Profile Manually
2. On the Partner profiles screen, select Partner profiles Partner type LS. 3. Choose New .
Page 42 of 70

4. On the right top area of Partner profiles screen, Make following entry: Field name Partner Number Description User action and values for example: ET6CLNT104 Note Sales Logical System Name The system assigns this number if you create a master record in an application (for example, purchasing, sales). The EDI partner is identified uniquely via the partner number and partner type. If you define your own partner types, they are also identified by this number. 5. On the Partner profiles screen, select Post processing: permitted agent. 6. Make the following entries: Field name Type Description Agent type User action and values US Note Agent type
Classifies the recipient of error notifications.
Examples
'US': An individual agent is notified. O: Agent type is an organizational unit: all persons assigned to this organizational unit are notified.
Dependencies
Individual persons are assigned to the positions, organizational units etc. in the PD Organizational Model (PD-ORG).
Page 43 of 70

Field name Agent Description User action and values AM-MUSTER Note Permitted users: ID
Specifies the job (person or group of people) to be notified if processing errors occur on the IDoc interface. You can define up to three different jobs: In the inbound or outbound partner profiles for special partners, messages and direction. In the general partner profiles for special partners. In the general IDoc Administration settings.
Use
If an error occurs, only one (the most specific) job is notified. If an error occurs in the ORDERS message for partner HUGH, the system first attempts to determine whether a job responsible for ORDERS and HUGH is defined. If this is not the case, the job defined for HUGH (required entry) is notified. The IDoc administrator is notified if HUGH does not exist at all in the partner profiles.
Examples
If the recipient type is 'US' ('user'), enter the name of the SAP user who is to be notified. If the recipient type is 'O' ('organizational unit'), enter the organizational unit whose personnel are to be notified.
Dependencies
This specification depends on how you have configured the PD Organizational Model (PDORG).
Lang.
Language of notification .
EN
If an error occurs, SAPoffice notifies the permitted user in this language.
7. Choose Save
If the partner already exists, you can change the partner or choose a different customer. If the customer number doesnt exist in your system, an error message pops up: Please enter a permitted partner number.
Result
Partner profile is created successfully.
Page 44 of 70
3.3.2 Use
Partner Profile Inbox
Inbound parameters in partner profile are created at the supplier side.
Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu WE20 Basis Components Application Link Enabling Modeling and Implementing Business Processes Partner profiles and Time of processing Maintain Partner Profile Manually
2. On the Partner profiles screen, select Partner profiles Partner type LS <Sales Logical System Name>, for example, ET6CLNT104. 3. On the Partner profiles screen, choose Insert under Inbound parmtrs Field name Partn. funct. Description Partner function of sender User action and values Note As an optional parameter, the partner function containing the sender and the recipient can be specified. Example: 'LF' for 'vendor' or 'AG' for 'sold-to party'. SNDPFC, SNDPRN and SNDPRT provide a unique ID for the sender. They are among the key fields in the partner profiles, which are used in inbound processing, for example, to determine the process code and therefore the internal processing for the IDoc. Therefore, if the sender function has been specified in the inbound partner profiles, the external system must maintain the field with the corresponding value. Message type WNTYCF In EDI, message types are normally assigned to SAP document types uniquely. Their names correspond as much as possible to those of the UN/EDIFACT standard. ALE scenarios, on the other hand, often have no EDIFACT correspondence, for example when master data is transmitted. Example ORDERS for purchase order data INVOIC for invoice data .
4. On the Partner profiles: Inbound parameters screen, make the following entries:
Page 45 of 70

5. On the bottom area of the Partner profiles screen: Inbound parameters, select Inbound options tab. 6. Make the following entries: Field name Process code Description Inbound Process Code User action and values WTYIV Note The IDoc interface uses the process code to find the business process, which controls the conversion of the IDoc into the SAP document. If you select the syntax check, the IDoc Interface terminates the processing if a syntax error is found. If you do not select the syntax check, the IDoc Interface continues the processing. You receive a message that a syntax error was found. Trigger Immediately 7. Choose Save. 8. Repeat step 1 - 7 to enter the following entries: Partner type LS Partner Number <Sales Logical System Name> Message Type WNTYRQ Partner function Message Code Process code WTYIC Trigger immediately X X The inbound IDoc is processed immediately.
Syntax Check
Please enter your own Sales logical system name in the field Partner Number, for example, ET6CLNT104.
3.3.3 Use
Maintaining a tRFC Port
A port is a group of technical attributes of a communication channel. This is required for dispatching messages to logical systems
Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu WE21 IMG Basis Component Application Link Enabling (ALE) Sending and Receiving Systems Systems in Network Asynchronous Processing Assigning Ports Define Port
2. On the Ports in IDoc processing screen, choose the Transactional RFC folder in the tree structure.
Page 46 of 70

3. Choose Create. 4. In the dialog box displayed, choose own port name. Enter the port name Z_AUTO. 5. On the screen for creating a tRFC port, enter the following information: Field name Description RFC destination Description User action and values tRFC Port BP Automotive Sales for example : ET6CLNT104 Comment
Sales Logical System Name
The RFC destination here should enter the destination this client is to communicate, for example, you should enter the RFC destination of the relevant Supplier client. 6. Choose Save.
Result
A port is created in system successfully.
3.3.3.1 3.3.4 Use
Maintaining a tRFC Port pointing to same client Maintaining a File Port
A port is description of the channel used by the SAP system for communicating with the external system during electronic data interchange. For Example: most EDI subsystems read IDocs in the form of sequential files, that is, the port type File is used. In this section you can define the file port. This is required for dispatching messages to logical systems. The port is assigned to a partner system in the partner profile.
Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu WE21 Basis Components Application Link Enabling Sending and Receiving Systems Systems in Network Asynchronous Processing Assigning Ports Define Port
2. On the Ports in IDoc processing screen, select Ports File on the left area of screen. 3. Choose New. 4. On the right area of Ports in IDoc processing screen, make following entries: Field name Port Description Version Description Port Name User action and values YEDIFILE Automotive EDI File Port IDoc record types SAP Release 4.x Note
Page 47 of 70

5. On the right bottom area of Ports in IDoc processing screen, select Outbound file tab. 6. Make following entries: Field name Physical directory Description The file is uniquely identified via the directory (path) and their names. User action and values /usr/sap/<your system ID>/SYS/global/ for example: /usr/sap/ET6/SYS/ global/ Note for example: under the UNIX operating system, /usr/sap/ET6/SYS/global/ Under the Windows operating system: \\sapdevdb\sapmnt\ET6\SYS\globa l\ Do not forget the last slash, as the file name is simply appended as a directory! In the example ET6 is the name of the SAP system. Function Module EDI_PATH_CREA TE_USERNAME In order to prevent unprocessed files being overwritten, you use function modules which generate file or directory names dynamically, that is to say, at runtime. For the output value every function module must deliver a "complete file name", that is, a character string from directory and file names. The file system then operates with these complete names. You can change the function module as you wish. To get all possible function modules, select F4 Help
You can choose Access Test to check the access permit to the folder you defined. 7. On the right bottom area of Ports in IDoc processing screen, select Inbound file tab. 8. Make following entries: Field name Physical directory Description The file is uniquely identified via the directory (path) and their names. User action and values /usr/sap/<your system ID>/SYS/global/ Note When system automatically proposes a directory, do not change the system proposal. for example: \\PWDF2756\sapET6root\usr\sap\ET6\SYS\global\
Page 48 of 70

Field name Inbound file Description User action and values Inbound Note Here you can specify a fixed name for the file, in which the IDocs from external systems (for example EDI subsystem) are transferred. SAP however recommends that the external system starts the inbound processing in the R/3 System and notifies what the transferred file is called (Parameter from startrfc). The field is then ignored. In general SAP recommends using dynamic file names, that is, variable file names generated at runtime, in order to prevent the overwriting of nonprocessed files. 9. On the right bottom area of Ports in IDoc processing screen, select Status file tab. 10. Make following entries: Field name Physical directory Description The file is uniquely identified via the directory ("path") and their names. User action and values /usr/sap/<your system ID>/SYS/global/ Note When system automatically proposes a directory, do not change the system proposal. for example: \\PWDF2756\sapET6root\usr\sap\ET6\SYS\global\
Inbound file
Status
Here you can specify a fixed name for the file, in which the status records from external systems (for example EDI subsystem) are transferred. SAP however recommends that the external system starts the status processing in the R/3-System and notifies what the transferred file is called (Parameter from startrfc). In this case the field is ignored. In general SAP recommends using dynamic file names, that is to say variable file names generated at runtime, in order to prevent the overwriting of non-processed files.
11. Choose Save.
Result
A file port is created in system successfully.
3.3.5 Use
Activating IDoc Inbound
The purpose of this activity is to activate IDoc Inbound Processing.
Page 49 of 70
This step only needs to be carried out once. If the system IDoc Inbound is already active, this step can be skipped.
Procedure
1. Access the activity using one of the following navigation options: SAP Menu Transaction Code Tools ABAP Workbench Development ABAP Editor SE38
2. On the ABAP Editor: Initial Screen, enter program RSEINBEV. 3. Choose Display. If the program is already Active, skip the rest of this step. 4. Choose Activate. 5. Confirm the message.
Result
A successful message is displayed.
3.4 Creating Claim Type YA02

Use
The purpose of this activity is to define the claim type YA02 used in warranty processing.
Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu OWTY Warranty Claim Processing Define Warranty Claim Types
2. On the initial screen, choose New Entries. 3. On the Detail view screen, maintain the following data: Clai m Type YA02 Description Pricing Schem a WT000 2 Division Messa ge Schem a WTY00 1 Partne r Det.Pr c C2 Reimburse r Partner Profile VN Partner Reimbu rs. V7102 Claiman t Partner Role AS
BP Auto Precrediting Distributi on Channel Z1
Sales Org Z001
Purch. Organization
Version Currency EUR
Plant
Z1
BP01
Page 50 of 70
Layout W/O Nav. tree SAPO
Layout W Nav. tree SAP
Action Control YA10
Start Process Status B001
Start Category IC
Field Name Split Criterion HERST
Item Type Group 00
Document Type Customer Posting WP
Document Type Vendor Posting WR
AcctDetProced KOFI00
Page 51 of 70
4. Choose Save (Ctrl + S).
Result
Claim type is created.
Page 52 of 70
3.5 Creating Claim Type YA01

Use
The purpose of this activity is to define the claim type YA01 used in warranty processing.
Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu OWTY Warranty Claim Processing Define Warranty Claim Types
2. On the initial screen, choose New Entries. 3. On the Detail view screen, maintain the following data: Clai m Type YA01 Description Pricing Schem a WT000 2 Division Messa ge Schem a WTY00 1 Partne r Det.Pr c C2 Reimburse r Partner Profile VN Partner Reimbu rs. Claiman t Partner Role AS
BP Auto YA01
Sales Org BP0X Layout W/O Nav. tree SAPO
Distributi on Channel 03 Layout W Nav. tree SAP
Purch. Organization
Version Currency EUR
Plant
01 Action Control YA11 Start Process Status B001
BP0X Field Name Split Criterion HERST Item Type Group 00
Start Category IC
Document Type Customer Posting WP 5. Choose Save (Ctrl + S).
Document Type Vendor Posting WR
AcctDetProced KOFI00
Result
Claim type is created.
3.6 Creating Notification Type

Use
The purpose of this activity is to define quality notification type.
Page 53 of 70
Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu SPRO Quality Management Quality Notifications Notification Creation Notification Types Define Notification Type
2. On the initial screen, choose New Entries. 3. On the New Entries: Details of Added Entries Screen, maintain the following data: Field name Notification Type Description Notif. cat Notification origin Catalog Profile Early no. alloc. Number Range Description User action and values Y9 BP Customer Compl. 02 Q1 Customer Complaint QM0000001 X 02 Note
4. Choose Save.
Result
The notification Type is created.
3.7 Defining Warranty Claim Groups

Use
The purpose of this activity is to defined warranty Claim Groups for Pre-Credit.
Procedure
1. Access the activity using one of the following navigation options: Transaction Code OWTY
Page 54 of 70

IMG Menu Warranty Claim Processing Warranty Claim Define Warranty Claim Groups
2. On the Change View: Warranty Claim Groups Overview screen, choose New Entries. 3. On the New Entries: Details of Added Entries Screen, maintain the following data: Field name Claim Group Description Claim Group User action and values PREC Pre-credit Note
4. Choose Save.
Result
Warranty Claim Group is created.
3.8 Defining Status for Parts to Be Returned

Use
In this activity you define status that you require for warranty processing with parts to be returned.
Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu OWTY Warranty Claim Processing Warranty Claim Warranty Claim Items Define Status for Parts to Be Returned
2. On the Change View Status for Parts that Have to Be Returned: Overview screen, choose New Entries. 3. Maintain the following data: Field name Partner Parts to Be Returned StsPrtsRtn Status of Parts to Be Returned Partner Parts to Be Returned StsPrtsRtn User action and values Claimant 4 Completed Reimburser 4 Selected Note Selected
Page 55 of 70

Status of Parts to Be Returned Completed
4. Choose Save.
Result
Status for parts to be returned defined.
3.9 Defining Message Type

Use
In this activity, you define the message types for message determination in Warranty Processing.
Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu OWTY Warranty Claim Processing Warranty Claim Message Determination Define Message Types
2. On the Display View Output Types: Overview screen, choose Display Change (Ctrl+F1). 3. On the Change View Output Types: Overview screen, select WTOC item to choose Details. 4. On the Change View Output Types: Details screen, make the following entries; Field name Access Sequence User action and values 0005 Note
Page 56 of 70
5. Choose Save.
3.10 Defining Control Data

3.10.1 Use
The purpose of this activity is to define actions used in warranty processing.
Defining Actions
Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu OWTY Warranty Claim Processing Control Data Process Control Define Actions
2. On the initial screen, choose New Entries. 3. Maintain the following data:
Page 57 of 70

Action YA* YA10 A Interlinking Action Displayed in Action Box A Interlinking Action Displayed in Action Box A Interlinking Action Displayed in Action Box F Elementary Action Displayed in Action Box T Elementary Action Hidden in Action Box V Interlinking Action Hidden in Action Box T Elementary Action Hidden in Action Box Action Type Description All YA* actions 1st step - Check WTY & Credit Memo Post 2nd step - GR & Version to Reimburser 3rd step - To Claimant & Debit Memo Post Complete Claim WTY04_CL AIM_CLOS E Y_WTY04_ GR_QSTOC K T061, T062 A200, T810, A040, YA66, A008 YA65, A070 Function Module Action Sequence
YA11
YA12
YA13, A043
YA50
YA62
Post goods receipt to Qstock Split Groups Proposal With Dialog Box Rel. IC-Version for sending
YA65
YA66
Y_WTY04_ VER_IC_SE ND
YA10:
Page 58 of 70
YA11:
YA12:
Page 59 of 70

YA50:
YA62:
YA65:
Page 60 of 70
YA66:
4. Choose Save.
Result
The actions are defined.
3.10.2 Use
Defining Action Controls
The purpose of this activity is to define action controls.
Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu OWTY Warranty Claim Processing Control Data Process Control Define Action Controls
Page 61 of 70

2. On the initial screen, choose New Entries. 3. On the New Entries: Details of Added Entries Screen, maintain the following records: Field name Action Control Action Control Description User action and values YA10 Processor Actions Note
4. Choose Enter. 5. Double-click Action Matrix, and on the Change View Action Matrix: Overview Screen, maintain the following data: Action Control YA10 YA10 YA10 YA10 YA10 YA10 YA10 YA10 YA10 YA10 YA10 YA10 YA10 YA10 YA10 YA10 YA10 B001 B001 B001 B001 B002 B002 B002 B002 B002 B002 B040 B040 B040 B040 B040 B060 Start Processing Action A* T* A* T* YA* YA10 A* T* T060 YA* YA10 YA66 A* T* T060 YA* YA50 T065 Target Processing B002 B002 B002 B002 B002 B040 B002 B002 B060 B002 B040 B040 B040 B040 B060 B040 B060 B040
Page 62 of 70
6. Choose Save. 7. Repeat steps 2 to 6 for YA11 with the following data: Field name Action Control Action Control Description User action and values YA11 Reimburser Actions Note
Action Matrix: Action Control YA11 YA11 YA11 YA11 YA11 YA11 YA11 B001 B001 B002 B002 B002 StartProcessing Action A* T* A* T* A* T* T060 Target Processing B002 B002 B002 B002 B002 B002 B060
Page 63 of 70
Result
The action controls are defined.
3.10.3 Use
Assigning Function Codes to Action Codes
The purpose of this activity is to assign the function code to the action code.
Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu OWTY Warranty Claim Processing Control Data Processing Control Assign Function Code to Action Code
2. On the Change View: Assign Function Code to Action Code Overview screen, choose New Entries and enter the following data: Field name Function Entry in Command fld. Action Function Entry in Command fld. Action Function Entry in Command fld. Action Function Entry in Command fld. Action Function Entry in Command fld. Action Function Entry in Command fld. Action Function Entry in Command fld. Action User action and values YA10 YA10 YA11 YA11 YA12 YA12 YA50 YA50 YA62 YA62 YA65 YA65 YA66 YA66 Note
Page 64 of 70
3. Choose Save.
3.10.4 Use
Defining Copy Procedure
The purpose of this activity is to create the copying control.
Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu OWTY Warranty Claim Processing Control Data Copying Control Define Copy Procedure
2. On the initial screen, choose New Entries. 3. On the New Entries: Overview of Added Entries Screen, maintain the following data: Field name Copy Procedure Description of Copy Procedure Description User action and values Y1 BP Standard Note
4. Choose Save.
3.10.5 Use
Assigning Copy Procedure to Claim Type
The purpose of this activity is to assign copy procedure to claim type.
Procedure
Page 65 of 70

1. Access the activity using one of the following navigation options: Transaction Code IMG Menu OWTY Warranty Claim Processing Control Data Copying Control Assign Copy Procedures to Claim Type
2. On the initial screen, choose New Entries. 3. On the New Entries: Overview of Added Entries screen, maintain the following data: Claim Type YA01 YA02 YA02 YA02 Source Categor y IC IC IV OV Target Categor y OC OV OC IV Copy Profil e Y1 Y1 Y1 Y1 X X CopyMATPric e CopyFRPric e CopySUBLPric e X X X X
Result
Copying Procedure is settled.
3.11 Layout Settings

3.11.1 Use
The purpose of this activity is to create the pushbutton on the warranty claim screen.
Defining Pushbutton Profile
Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu OWTY Warranty Claim Processing Layout Define Pushbutton Profiles
Page 66 of 70

2. On the initial screen, choose New Entries. 3. On the New Entries: Overview of Added Entries screen, maintain the following data: Pushbutton Profile YA_PROFILE Profile Description BP Auto for Processor Action Control YA10
4. Choose Save.
3.11.1.1 Use
Assigning Action Controlling
The purpose of this activity is to assign the action controls to the pushbutton profile.
Procedure
2. On the initial screen, select the pushbutton profile you created in the previous step and double click Action Control. 3. On the Change View Action Control Overview screen, choose New Entries, and maintain the following data: Action Control YA10 YA10 YA10 YA10 Category IC Incoming Customer (IC) IV Incoming Vendor (IV) OC Outgoing Customer (OC) OV Outgoing Vendor (OV)
Page 67 of 70
4. Choose Enter. 5. Choose Save
3.11.1.2 Use
Defining Pushbutton Profile - Assigning Action Code
The purpose of this activity is to assign the actions to the pushbutton profile.
Procedure
2. On the initial screen, select the pushbutton profile you created in the previous step and double click Actions. 3. On the Change View Actions: Overview Screen, choose New Entries, and maintain the following data: Function W_BUTTON1 W_BUTTON2 W_BUTTON3 W_BUTTON4 W_BUTTON5 W_BUTTON6 W_BUTTON7 Action Code YA10 YA62 YA11 A100 A870 A019 YA12 Text Pushbutton WTY Check & Post to FI Q-stock Version To Reimburser Delivery Release From Reim. To Claimant
Page 68 of 70
4. Choose Enter. 5. Choose Save.
Result
The pushbutton profile is created.
3.11.1.3 Use
Defining Message Groups
The purpose of this activity is to define message groups.
Procedure
1. Access the activity using one of the following navigation options: Transaction Code IMG Menu OWTY Warranty Claim Processing Layout Define Message Groups
2. On the initial screen, choose New Entries. 3. On the New Entries: Details of Added Entries Screen, maintain the following data: Message Group KL YAGR Description Delivery w/o Charge Goods receipt into Q-Stock
Page 69 of 70
4. Choose Save.
Result
Message Groups YAGR and KL are created.
3.12 Manual Step

3.12.1 Use
The purpose of this activity is to maintain document type determination.
Maintaining Document Type Determination for Warranty
Procedure
1. Access the activity using one of the following navigation options: Transaction Code YWTY_DM
2. On the Change View Document Type Determination for Warranty: Overview screen, choose New Entries, and make the following entries: Field name Object Typ Claim Group WtyClm Type Warranty Claim Type Description Object Type User action and values EQUI PREC YA01 Note Equipment Pre-credit
3. Choose Enter to confirm your entries.
4. Choose Save.
Result
Warranty document type determination is defined.
Page 70 of 70

Warranty Processing Pre Credit ConfigGuide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Warranty Processing Pre Credit ConfigGuide

Uploaded by

Copyright:

Available Formats

Warranty Processing_Pre Credit_ConfigGuide