Warranty Processing_Pre Credit_ConfigGuide

Warranty Processing
Configuration Guide

Warranty Processing_Pre Credit_ConfigGuide

Page 2 of 70

Warranty Processing_Pre Credit_ConfigGuide

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 Assigning Function Codes to Action Codes...........................................................12 Manual Step.............10.....................10.......11 Layout Settings................70 Page 4 of 70 .....................10.......................................5 Assigning Copy Procedure to Claim Type.................................................4 Defining Copy Procedure.....Warranty Processing_Pre Credit_ConfigGuide 3.......11..............................2 Defining Action Controls......10.............64 3..1 Maintaining Document Type Determination for Warranty.................................65 3......65 3...................... 66 3............................... 61 3.............................12................................................................... 66 3........ 70 3...........................................................................................................1 Defining Pushbutton Profile....

1.1 Prerequisites 2. 2 Preparation 2. use the Best Practices Installation Assistant. 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.Warranty Processing_Pre Credit_ConfigGuide 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.1. Maintaining QM Standard Setting Catalogs Procedure Page 5 of 70 .1 Building Blocks Before you start installing this building block.1 Use The purpose of this activity is to copy entries for QM standard settings for catalogs from client 000 to the installation client.1 QM Standard Setting 3.

The system displays the result.1. Access the activity using one of the following navigation options: Transaction Code QCCK 2.Warranty Processing_Pre Credit_ConfigGuide 1. Confirm the Do you want to copy customizing to your client? dialog box with Yes. 4. Result You have copied the QM Standard Settings for Catalogues from client 000 to your installation client. 3. Procedure Page 6 of 70 . Choose Back. 3.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.

3. make the following entries: Field Function Group Short Text User action and values Y_WTY_AT Warranty Development Page 7 of 70 .1 Creating Function Group Procedure 1.Warranty Processing_Pre Credit_ConfigGuide 1.2. In the Create Function Group dialog box. Access the activity using one of the following navigation options: Transaction Code QCCM 2. 4. Confirm the Do you want to copy customizing to your client? Dialog box with Yes. Access the activity using one of the following navigation options: SAP Menu Transaction Code Tools → ABAP Workbench → Development → Function Builder SE37 2. 3. Result You have copied the QM Standard Settings for Quality Notifications from client 000 to your installation client. The system displays the result. Choose Back. 3. On the Function Builder: Initial Screen choose from the menu: Goto → Function Group → Create Group.2 Manual Step 3.

Go Back to the SAP Easy Access screen. In the Create Object Directory Entry dialog box. Access the activity using one of the following navigation options: Page 8 of 70 .2. Make the following entries: Field Function Group Short Text User action and values Y_WTY_TABLE Extended Table Maintenance (Generated) 7. Choose Save.Warranty Processing_Pre Credit_ConfigGuide 4. Result The Function Groups are created. 6. 5. choose Local Object. 3. Repeat steps 2 – 5 to create function group Y_WTY_TABLE.2 Changing Function Group Procedure 1.

Choose Continue. On the ABAP Editor. " Function Modules ******************************************************************* * User-defined Include-files (if necessary). make the following entries: Field Function Group 4.. " Global Data INCLUDE LY_WTY_ATUXX. choose from the menu: Goto → Function Group → Change Group.. On the Change Function Group dialog box.Warranty Processing_Pre Credit_ConfigGuide SAP Menu Transaction Code Tools → ABAP Workbench → Development → Function Builder SE37 2. 5... * ******************************************************************* * INCLUDE LY_WTY_ATF. " Subprograms * INCLUDE LY_WTY_ATO. 6. * ******************************************************************* INCLUDE LY_WTY_ATTOP. choose Main program.. In the Change Function Group dialog box.. check the following code: ******************************************************************* * System-defined Include-files. On the Function Builder: Initial Screen. " PAI-Modules User action and values Y_WTY_AT Page 9 of 70 . " PBO-Modules * INCLUDE LY_WTY_ATI. choose Display <-> Change. On the following screen. 3. 7.

Choose Save. 10. Choose Continue. On the Inactivate Object for user XXXXXXXX View. " Function Modules Description SAPLY_WTY_AT LY_WTY_ATTOP User action and values Selected Selected Note Page 10 of 70 . Field name Object name Object name 11. 9. 12. Choose Activate. On the ABAP Editor check the following code: ******************************************************************* * System-defined Include-files. 14. Choose Back (F3). choose Cancel. Local Objects tab page. If the Change Function Group dialog box appears. " Global Data INCLUDE LY_WTY_TABLEUXX. Repeat steps 2 – 7 to change the function group Y_WTY_TABLE.Warranty Processing_Pre Credit_ConfigGuide 8. * ******************************************************************* INCLUDE LY_WTY_TABLETOP. 13.

Warranty Processing_Pre Credit_ConfigGuide Page 11 of 70 .

Local Objects tab page.Warranty Processing_Pre Credit_ConfigGuide 15. Description SAPLY_WTY_TABLE LY_WTY_TABLETOP User action and values Selected Selected Note 3. If the Change Function Group dialog box appears. On the Inactivate Object for user XXXXXXXX View. make the following entries: Field name Object name Object name 18. 17. 16. choose Cancel.2. 19. Choose Activate. Choose Continue. Choose Save. Procedure 1. 20. 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 . Choose Back. Go Back to the SAP Easy Access screen.3 Use Defining the Table YWTY_DM The purpose of this activity is to define the table.

Choose Create. On the Dictionary: Maintain Table screen. 6. Choose the tab Fields. 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. On the ABAP Dictionary: Initial Screen. make the following entries: Page 13 of 70 . Description Database Table Name User action and values YWTY_DM Note 4.Warranty Processing_Pre Credit_ConfigGuide 2. enter the following data: Field name Database Table 3. On the screen Dictionary: Maintain Table.

Warranty Processing_Pre Credit_ConfigGuide 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 .

10. 9. Choose ENTER to confirm your entries. Select the CLMGRP row.Warranty Processing_Pre Credit_ConfigGuide Field Name Entry 4 Field CLMTY Key Blank Initial Values Blank Data element WTY_CLMTY 7. Choose Enter to confirm your entries. On the screen Create Foreign Key YWTY DM-CLMGRP. and confirm the dialog box with Yes. Choose Foreign Keys . 11. Page 15 of 70 . 8. in the field Check table enter CWTY006.

. Page 16 of 70 . 14. Confirm the dialog box with Yes and save as local object. and go Back. 13. choose Technical Settings. Choose Save. Select the radio button Key fields/candidates.Warranty Processing_Pre Credit_ConfigGuide 12. enter the following entries: Field name Data class Size category 17. 20. Choose Activate to activate the table. Description User action and values APPL0 0 Note Result Table YWTY_DM has been defined. and fill the Cardinality with 1:1. 18. 19. 16. Choose Copy to confirm your entries. 15. On the screen Dictionary: Maintain Technical Settings. Choose Back to the SAP Easy Access screen. Choose No if warning message appears. On the Dictionary: Maintain Table screen.

On the Generate Table Maintenance Dialog: Generate Environment screen. Choose Create/change. Confirm the dialog box with Yes. make the following entries: Field name Generated Objects Table / View 3. 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.2. On the Generate Table Maintenance Dialog: Initial Table/View Screen. 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. 4.4 Use Defining Generating Table Maintenance Dialog YWTY_DM The purpose of this activity is to define the generate table maintenance dialog. 5.Warranty Processing_Pre Credit_ConfigGuide 3. Procedure 1. recording routine Set the indicator Page 17 of 70 . or user.

Warranty Processing_Pre Credit_ConfigGuide

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

Warranty Processing_Pre Credit_ConfigGuide
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

Warranty Processing_Pre Credit_ConfigGuide

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

make the following entries: Field Short Text User action and values Automotive . Access the activity using one of the following navigation options: SAP Menu Transaction Code Tools → ABAP Workbench → Development → Programming Environment → Messages SE91 2.2. Procedure 1.6 Use Creating Message Class The purpose of this activity is to create message class YEAT.Warranty Page 21 of 70 .Warranty Processing_Pre Credit_ConfigGuide 3. On the Message Maintenance Initial Screen. make the following entries: Field Message Class User action and values YEAT 3. On the Attributes tab page. Choose Create. 4.

K. Go Back to the SAP Easy Access screen. choose Local Object 7.Warranty Processing_Pre Credit_ConfigGuide 5. 3. 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. In the Create Object Directory Entry dialog box. Select the Messages tab page. Program run not O. make the following entries: Page 22 of 70 . Choose Save.K. Choose Save. Choose Create. 9.2. 6. 8. Result Message class YEAT is created.7 Business Add-Ins: Enhancement of Document Flow Procedure 1. 3. In the Business Add-In Builder: Create Implementation dialog box. make the following entries: Message Field 001 009 010 User action and values Material document & created when claim is saved Program run O.

14. 24. 8. 19. In the Information Window choose Continue. Load the source code from DOCUMENT_DISPLAY. choose Continue. Field Implementation Short Text 6. 5. Choose Save and Activate.txt under \MISC\ A20 folder on the DVD. choose Create Enhancement Implementation and make the following entries: Field Enhancement Implementation Short Text 9. On the appearing dialog box. Load the source code from ADD_DOCUMENT. On the Select or Create Enhancement Implementation screen. Go to the Interface tab page. Go Back to the IMG menu. choose Local Object. 15. On the appearing dialog box. Choose Back. 25. select Y_WTY_DOCU_ADD and choose Enter. 7.Warranty Processing_Pre Credit_ConfigGuide Field Implementation Name 4. 16. double click the method ADD_DOCUMENT. Choose Save. In the following screen. make the following entries. In the Create Object Directory Entry dialog box.txt under \MISC\ A20 folder on the DVD. choose Local Object. 17. 22. delete all of old source codes. 11. 12. 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. On the ABAP Editor. 21. On the ABAP Editor. In the Create Object Directory Entry dialog box. choose continue. 13. Choose Continue. Double click the other method DOCUMENT_DISPLAY. Choose Back. On the Business Add-In Builder: Change Implementation Y_WTY_DOCU_ADD screen. 23. 10.8 Business Add-Ins: Data Checking and Changing for Inbound IDocs Page 23 of 70 . delete all of old source codes. choose Activate. 20. Choose Save and then Activate. 18. On the Select or Create Enhancement Implementation screen. Choose Save.

On the following screen. 11. 15. 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. make the following entries. Repeat step 12-14 to activate method INTERPRET_IDOC. 12. Load the source code from CHECK_IDOC. Choose Activate. delete all of old source codes. In the Business Add-In Builder: Create Implementation dialog box. 14. Choose Continue (Enter). 13. choose Local Object. CHANGE_EXPORT_PARAMETERS and CHECK_PARTNER. make the following entries: Field Implementation Name 3. Choose Save. double click the method CHECK_IDOC. choose Continue. User action and values Change Inbound Warranty Idoc 3.Warranty Processing_Pre Credit_ConfigGuide Procedure 1. Choose Back. Double click method INTERPRET_ADDITIONAL_SEGMENT. In the Create Object Directory Entry dialog box. Choose Back. On the Interface tab page.9 Business Add-Ins: Data Checking and Changing for Outbound IDocs Procedure 1. On the ABAP Editor. and on the appearing dialog box. 6. 7. choose Continue. 10. 18. Access the activity using one of the following navigation options: Transaction Code OWTY Page 24 of 70 . On the appearing dialog box. 8.txt under \MISC\ A20 folder on the DVD. On the Business Add-In Builder: Change Implementation Y_WTY_IDOC_IN screen. 16. Choose Save and Activate. choose Activate. Go back to the IMG menu. 17. 9. 4. Field Implementation Short Text 5.2.

delete all of old source codes. On the Business Add-In Builder: Change Implementation Y_WTY_IDOC_OUT screen choose Activate.2. Choose Continue (Enter). Choose Save and then Activate. 7. On the Interface tab page. 12. Load the source code from CHANGE_SEGMENT. 10. Access the activity using one of the following navigation options: SAP Menu Transaction Code Tools → ABAP Workbench → Development → Function Builder SE37 2. double click the method CHANGE_SEGMENT. In the Business Add-In Builder: Create Implementation dialog box. On the following screen. 8. 9. 11. 4. make the following entries. 6. In the Function Builder: Initial Screen dialog box. Choose Save. choose Continue. choose Local Object.10 Creating Function Model: Good Receipt of Return Parts into Q-Stock Procedure 1. Choose Back. make the following entry: Field Function Module 3.txt under \MISC\ A20 folder on the DVD. User action and values Y_WTY04_GR_QSTOCK Page 25 of 70 . On the appearing dialog box. Field Implementation Short Text 5. make the following entries: Field Implementation Name 3. 13. Go Back to the IMG menu. 14. On the ABAP Editor. Choose Create. User action and values Change Outbound Warranty Idoc 3.Warranty Processing_Pre Credit_ConfigGuide 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 Create Object Directory Entry dialog box.

select the tab Import.Warranty Processing_Pre Credit_ConfigGuide 4. and make the following entries: Parameter Name IT_RCODE IV_RCODE_MAX IV_MODE IV_ACODE Type Spec. 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. TYPE TYPE TYPE TYPE Associated Type WTY_RCODE_TAB SYSUBRC WTY_MODE WTY_ACODE Optional X X X X Page 26 of 70 . 6. Choose Enter. On the following screen. On the following screen.

Select the tab Export. 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 .Warranty Processing_Pre Credit_ConfigGuide 7. Select the tab Changing. 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 Source Code 10. Load the source code from Y_WTY04_GR_QSTOCK. 11.Warranty Processing_Pre Credit_ConfigGuide 9.txt under \MISC\ A20 folder on the DVD. delete all of old source codes. On the ABAP Editor. Page 28 of 70 .

Warranty Processing_Pre Credit_ConfigGuide Page 29 of 70 .

Warranty Processing_Pre Credit_ConfigGuide Page 30 of 70 .

Warranty Processing_Pre Credit_ConfigGuide Page 31 of 70 .

Warranty Processing_Pre Credit_ConfigGuide Page 32 of 70 .

* Goods mvmt cv_bus2017(10) TYPE c VALUE 'BUS2017'. ls_pvwty TYPE pvwty. lt_pvwty TYPE pwty_pvwty_li_tab. lt_pvwty_dia TYPE wty_pvwty_dia_tab. pwty_pvwty_li_tab TYPE STANDARD TABLE OF pwty_pvwty_li WITH KEY pvguid pvcnt. DATA: ls_pnwtyv TYPE pnwtyv. cv_bus2032(10) TYPE c VALUE 'BUS2032'.Warranty Processing_Pre Credit_ConfigGuide FUNCTION Y_WTY04_GR_QSTOCK. Page 33 of 70 . DATA: lv_version_guid TYPE pvs_guid. CONSTANTS: cv_bus2222(10) TYPE c VALUE 'BUS2222'. *"---------------------------------------------------------------------*"*"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.

DATA: BEGIN OF i_errors OCCURS 0. ev_return_code = 1. DATA: s_head_01 TYPE bapi2017_gm_head_01. DATA: BEGIN OF lt_return OCCURS 0. *--. mat_doc LIKE mseg-mblnr. TYPE wty_pvwty_dia. 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. s_gm_code-gm_code = '05'. EXIT. CALL FUNCTION 'WTY07_CLEAR_DFLMESSAGES' EXPORTING iv_pnguid = cs_pnwtyh_dia-pnguid iv_dflmsg = 'YAGR' iv_versn = ls_pnwtyv_dia-versn. TYPE borident.Warranty Processing_Pre Credit_ConfigGuide ls_pnwtyv_dia ls_pvwty_dia lv_docno ls_obj_rolea ls_obj_roleb lv_reltype lv_dummy TYPE wty_pnwtyv_dia. INCLUDE STRUCTURE hrale_err. TYPE borident. ENDIF. DATA: BEGIN OF lt_items OCCURS 0. INCLUDE STRUCTURE bapiret2. endif. TYPE breltyp-reltype. mat_year LIKE mseg-mjahr.determine items of active IC-version CLEAR ls_pnwtyv. ev_return_code = 2. TYPE string. DATA: wrk_quan LIKE bapi2017_gm_item_create-entry_qnt. s_head_01-pstng_date = sy-datum. TYPE bapivbeln-vbeln. s_gm_code TYPE bapi2017_gm_code. DATA: END OF i_errors. INCLUDE STRUCTURE bapi2017_gm_item_create. IF iv_rcode_max > 0. Page 34 of 70 . DATA: END OF lt_return. exit. DATA: END OF lt_items.

lt_items-material = ls_pvwty-matnr. IF NOT lt_items[] IS INITIAL. * Select those items which have to be returned LOOP AT lt_pvwty into ls_pvwty where RETPA = 1. lt_items-stge_loc = 'Z001'. change the source code above *accordingly. lt_items-move_reas = space. Page 35 of 70 . CONCATENATE 'Claim ' cs_pnwtyh_dia-clmno INTO s_head_01-header_txt separated by space. CLEAR: mat_doc. lt_items-ref_date = sy-datum. In case the *storage location is not ‘YD03’. lt_items-entry_qnt = wrk_quan. lt_items-plant = cs_pnwtyh_dia-werks. 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.Warranty Processing_Pre Credit_ConfigGuide s_head_01-doc_date = sy-datum. ENDLOOP. * ‘YD03’ refers to the storage location for return parts. mat_year. "Grund der Bew. APPEND lt_items. wrk_quan = ls_pvwty-quant. lt_items-move_type = '503'. REFRESH lt_items. REFRESH: lt_return. SELECT single maktx FROM MAKT into lt_items-item_text WHERE MATNR = ls_pvwty-matnr AND SPRAS = sy-langu. CLEAR lt_items. * 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-entry_uom = ls_pvwty-meinh. s_head_01-pr_uname = sy-uname.

*--. CALL FUNCTION 'WTY07_MESSAGE_PROCESSING' EXPORTING * * * * * * * * * * * * * * Page 36 of 70 . MOVE cs_pnwtyh_dia-clmno TO ls_obj_rolea-objkey. ELSE. endif. modify CT_PVWTY_DIA index sy-tabix from ls_pvwty_dia transporting retpa. MESSAGE i001(YA71) WITH mat_doc into lv_dummy. 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. MOVE cv_bus2222 TO ls_obj_rolea-objtype. MESSAGE i001(YEAT) WITH mat_doc. MOVE mat_doc TO ls_obj_roleb-objkey. 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. ls_pvwty_dia-retpa = 3. ENDLOOP.Material document. DELETE lt_return. Change status of Parts to 3 .Warranty Processing_Pre Credit_ConfigGuide * LOOP AT lt_return WHERE type <> 'E' AND type <> 'A'. ev_return_code = 0.claim IF lt_return[] IS INITIAL. if sy-subrc = 0. MOVE cv_bus2017 TO ls_obj_roleb-objtype. ENDLOOP. LOOP AT lt_return. *--. PERFORM document_flow_create USING ls_obj_rolea ls_obj_roleb lv_reltype cs_pnwtyh_dia-pnguid."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. * Relationtype MOVE 'VONA' TO lv_reltype.

ENDLOOP. ENDFUNCTION. ENDIF.Object A CS_OBJ_ROLEA-LOGSYS = LV_OWN_LOGICAL_SYSTEM. * 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 B CS_OBJ_ROLEB-LOGSYS = LV_OWN_LOGICAL_SYSTEM. *--. ENDIF.Warranty Processing_Pre Credit_ConfigGuide 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.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 . ev_return_code = 4. DATA: LV_OWN_LOGICAL_SYSTEM TYPE TBDLS-LOGSYS. *&---------------------------------------------------------------------* *& 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. LV_MSGTXT TYPE STRING.

13. Version IC for sending Procedure 1. 12. IF SY-SUBRC <> 0. * 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.2. lt_items-stge_loc = 'YD03'.Warranty Processing_Pre Credit_ConfigGuide NO_MODEL =1 INTERNAL_ERROR = 2 UNKNOWN =3 OTHERS = 4. Choose Save and Activate.11 Creating Function Model: Rel. " document_flow_create In our solution we use the storage location for returnable parts ‘YD03’. Go Back the SAP Easy Access screen. ENDIF. ENDFORM. 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. ensure you change the value ‘YD03’ in the source code below. to your own storage location. Access the activity using one of the following navigation options: SAP Menu Transaction Code Tools → ABAP Workbench → Development → Function Builder SE37 2. If you wish to personalize your solution and change your storage location for returnable parts to another value. On the Function Builder: Initial Screen dialog box. make the following entries: Page 38 of 70 . 3.

make the following entries: Field Function Group Short Text User action and values Y_WTY_AT Rel. and make the following entries: Parameter Name IT_RCODE IV_RCODE_MAX IV_MODE Type Spec. Choose Create. Version IC for Sending 5.Warranty Processing_Pre Credit_ConfigGuide Field Function Module User action and values Y_WTY04_VER_IC_SEND 3. Select the tab Import. TYPE TYPE TYPE Associated Type WTY_RCODE_TAB SYSUBRC WTY_MODE Optional X X X Page 39 of 70 . 6. Choose Enter. On the following screen. 4.

Select the tab Changing. and make the following entries: Parameter Name CT_PRELID CS_PNWTYH_DIA CT_PNWTYV_DIA CT_PVWTY_DIA Type Spec.Warranty Processing_Pre Credit_ConfigGuide 7. Select the tab Source Code. Select the tab Export. Page 40 of 70 . 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. 10.txt under \MISC\ A20 folder on the DVD. Load the source code from Y_WTY04_VER_IC_SEND. TYPE Associated Type SYSUBRC Optional 8. delete all of old source codes. On the ABAP Editor. 11. and make the following entries: Parameter Name EV_RETURN_CODE Type Spec.

*"---------------------------------------------------------------------*"*"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 .Warranty Processing_Pre Credit_ConfigGuide FUNCTION Y_WTY04_VER_IC_SEND.

On the Partner profiles screen. Page 42 of 70 . select Partner profiles → Partner type LS. ENDFUNCTION. 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.1 Use Partner profiles for EDI communication are created at the supplier side. Only Basic Data Procedure 1. 3. 3.Warranty Processing_Pre Credit_ConfigGuide *" 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. Choose New .3. ev_return_code = 2. Go Back to the SAP Easy Access screen. Choose Save and Activate. ENDIF. EXIT. Partner Profile.3 EDI Communication General Settings 3. 13. 12. 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.

sales). Examples 'US': An individual agent is notified. On the right top area of Partner profiles screen. they are also identified by this number. purchasing. organizational units etc. select Post processing: permitted agent. Dependencies Individual persons are assigned to the positions. On the Partner profiles screen. Page 43 of 70 . 5.Warranty Processing_Pre Credit_ConfigGuide 4. 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. in the PD Organizational Model (PD-ORG). The EDI partner is identified uniquely via the partner number and partner type. ‘O’: Agent type is an organizational unit: all persons assigned to this organizational unit are notified. 6. If you define your own partner types. Make the following entries: Field name Type Description Agent type User action and values US Note Agent type Classifies the recipient of error notifications.

an error message pops up: Please enter a permitted partner number. Examples If the recipient type is 'US' ('user'). If this is not the case. enter the organizational unit whose personnel are to be notified. Language of notification . In the general IDoc Administration settings. Page 44 of 70 . enter the name of the SAP user who is to be notified. messages and direction. You can define up to three different jobs: In the inbound or outbound partner profiles for special partners. The IDoc administrator is notified if HUGH does not exist at all in the partner profiles. SAPoffice notifies the permitted user in this language. If the recipient type is 'O' ('organizational unit'). Dependencies This specification depends on how you have configured the PD Organizational Model (PDORG). Result Partner profile is created successfully. EN If an error occurs. only one (the most specific) job is notified. you can change the partner or choose a different customer. 7.Warranty Processing_Pre Credit_ConfigGuide 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. the job defined for HUGH (required entry) is notified. If the customer number doesn’t exist in your system. the system first attempts to determine whether a job responsible for ORDERS and HUGH is defined. If an error occurs in the ORDERS message for partner HUGH. Use If an error occurs. Lang. Choose Save If the partner already exists. In the general partner profiles for special partners.

on the other hand. On the Partner profiles screen. Example: 'LF' for 'vendor' or 'AG' for 'sold-to party'. SNDPFC. On the Partner profiles screen. ALE scenarios. if the sender function has been specified in the inbound partner profiles. On the Partner profiles: Inbound parameters screen. for example. 4. choose Insert under Inbound parmtrs Field name Partn. funct. Message type WNTYCF In EDI. Their names correspond as much as possible to those of the UN/EDIFACT standard. the external system must maintain the field with the corresponding value. to determine the process code and therefore the internal processing for the IDoc. Procedure 1. Description Partner function of sender User action and values Note As an optional parameter. 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. They are among the key fields in the partner profiles. for example when master data is transmitted. Therefore. the partner function containing the sender and the recipient can be specified. ET6CLNT104. which are used in inbound processing.Warranty Processing_Pre Credit_ConfigGuide 3. Example   ORDERS for purchase order data INVOIC for invoice data . for example. message types are normally assigned to SAP document types uniquely. SNDPRN and SNDPRT provide a unique ID for the sender. often have no EDIFACT correspondence.2 Use Partner Profile Inbox Inbound parameters in partner profile are created at the supplier side. select Partner profiles → Partner type LS → <Sales Logical System Name>.3. make the following entries: Page 45 of 70 . 3.

On the bottom area of the Partner profiles screen: Inbound parameters. choose the Transactional RFC folder in the tree structure.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. the IDoc Interface terminates the processing if a syntax error is found. 3. Repeat step 1 . 6. 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.3. select Inbound options tab.Warranty Processing_Pre Credit_ConfigGuide 5. Page 46 of 70 . 8. Trigger Immediately 7. If you do not select the syntax check. This is required for dispatching messages to logical systems Procedure 1. You receive a message that a syntax error was found.3 Use Maintaining a tRFC Port A port is a group of technical attributes of a communication channel. which controls the conversion of the IDoc into the SAP document. the IDoc Interface continues the processing. 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. On the Ports in IDoc processing screen. If you select the syntax check. for example. Syntax Check X Please enter your own Sales logical system name in the field Partner Number. ET6CLNT104. Choose Save.

Procedure 1.Warranty Processing_Pre Credit_ConfigGuide 3. In this section you can define the file port. The port is assigned to a partner system in the partner profile. 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: most EDI subsystems read IDocs in the form of sequential files. the port type File is used. 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.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. Choose New. 3. choose own port name. In the dialog box displayed. Choose Save.1 3. This is required for dispatching messages to logical systems. you should enter the RFC destination of the relevant Supplier client. 5. 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. Result A port is created in system successfully. that is. 4. On the Ports in IDoc processing screen. Choose Create.3. 4.3. for example.x Note Page 47 of 70 . On the screen for creating a tRFC port. select Ports → File on the left area of screen. Enter the port name Z_AUTO. 6. 3. On the right area of Ports in IDoc processing screen.3.

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

Result A file port is created in system successfully. in order to prevent the overwriting of non-processed files. 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 which the IDocs from external systems (for example EDI subsystem) are transferred. Make following entries: Field name Physical directory Description The file is uniquely identified via the directory ("path") and their names. variable file names generated at runtime. The field is then ignored.3. In general SAP recommends using dynamic file names. 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). On the right bottom area of Ports in IDoc processing screen. do not change the system proposal. Page 49 of 70 . that is. Choose Save. 11.5 Use Activating IDoc Inbound The purpose of this activity is to activate IDoc Inbound Processing. in which the status records from external systems (for example EDI subsystem) are transferred. User action and values /usr/sap/<your system ID>/SYS/global/ Note When system automatically proposes a directory. in order to prevent the overwriting of nonprocessed files. 3. that is to say variable file names generated at runtime. select Status file tab. 9. for example: \\PWDF2756\sapET6root\usr\sap\ET6\SYS\global\ Inbound file Status Here you can specify a fixed name for the file.Warranty Processing_Pre Credit_ConfigGuide Field name Inbound file Description User action and values Inbound Note Here you can specify a fixed name for the file. 10. In this case the field is ignored. In general SAP recommends using dynamic file names.

3. maintain the following data: Clai m Type YA02 Description Pricing Schem a WT000 2 Division Messa ge Schem a WTY00 1 Partne r Det. Organization Version Currency EUR Plant Z1 BP01 Page 50 of 70 . On the Detail view screen. Choose Display.Pr c C2 Reimburse r Partner Profile VN Partner Reimbu rs. enter program RSEINBEV. Confirm the message. If the program is already Active. Result A successful message is displayed. Access the activity using one of the following navigation options: SAP Menu Transaction Code Tools → ABAP Workbench → Development → ABAP Editor SE38 2.4 Creating Claim Type YA02 Use The purpose of this activity is to define the claim type YA02 used in warranty processing. skip the rest of this step. Access the activity using one of the following navigation options: Transaction Code IMG Menu OWTY Warranty Claim Processing → Define Warranty Claim Types 2. 5. On the initial screen. 4. On the ABAP Editor: Initial Screen. V7102 Claiman t Partner Role AS BP Auto Precrediting Distributi on Channel Z1 Sales Org Z001 Purch.Warranty Processing_Pre Credit_ConfigGuide This step only needs to be carried out once. Procedure 1. 3. this step can be skipped. Procedure 1. choose New Entries. 3. If the system IDoc Inbound is already active. Choose Activate.

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 .Warranty Processing_Pre Credit_ConfigGuide Layout W/O Nav.

Result Claim type is created. Choose Save (Ctrl + S).Warranty Processing_Pre Credit_ConfigGuide 4. Page 52 of 70 .

maintain the following data: Clai m Type YA01 Description Pricing Schem a WT000 2 Division Messa ge Schem a WTY00 1 Partne r Det. Procedure 1. choose New Entries. tree SAP Purch. Document Type Vendor Posting WR AcctDetProced KOFI00 Result Claim type is created.6 Creating Notification Type Use The purpose of this activity is to define quality notification type. On the Detail view screen. 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. On the initial screen. 3. 3.Warranty Processing_Pre Credit_ConfigGuide 3. Page 53 of 70 .5 Creating Claim Type YA01 Use The purpose of this activity is to define the claim type YA01 used in warranty processing. Choose Save (Ctrl + S). tree SAPO Distributi on Channel 03 Layout W Nav. Claiman t Partner Role AS BP Auto YA01 Sales Org BP0X Layout W/O Nav.Pr c C2 Reimburse r Partner Profile VN Partner Reimbu rs. Access the activity using one of the following navigation options: Transaction Code IMG Menu OWTY Warranty Claim Processing → Define Warranty Claim Types 2.

Result The notification Type is created. Number Range Description User action and values Y9 BP Customer Compl. Choose Save. 02 Q1 Customer Complaint QM0000001 X 02 Note 4. On the initial screen.Warranty Processing_Pre Credit_ConfigGuide Procedure 1. 3. choose New Entries. Access the activity using one of the following navigation options: Transaction Code OWTY Page 54 of 70 . maintain the following data: Field name Notification Type Description Notif. Procedure 1. cat Notification origin Catalog Profile Early no.7 Defining Warranty Claim Groups Use The purpose of this activity is to defined warranty Claim Groups for Pre-Credit. alloc. 3. On the New Entries: Details of Added Entries Screen. 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.

choose New Entries. Result Warranty Claim Group is created. On the New Entries: Details of Added Entries Screen. 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 . 3. 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. choose New Entries. On the Change View” Status for Parts that Have to Be Returned”: Overview screen.Warranty Processing_Pre Credit_ConfigGuide IMG Menu Warranty Claim Processing → Warranty Claim → Define Warranty Claim Groups 2. 3. maintain the following data: Field name Claim Group Description Claim Group User action and values PREC Pre-credit Note 4.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. On the Change View: “Warranty Claim Groups” Overview screen. 3. Choose Save.

9 Defining Message Type Use In this activity. make the following entries. 4. Result Status for parts to be returned defined.Warranty Processing_Pre Credit_ConfigGuide Status of Parts to Be Returned Completed 4. select WTOC item to choose Details. Procedure 1. On the Display View” Output Types”: Overview screen. On the Change View” Output Types”: Details screen. choose Display → Change (Ctrl+F1). 3. Choose Save. 3. On the Change View” Output Types”: Overview screen. you define the message types for message determination in Warranty Processing. Field name Access Sequence User action and values 0005 Note Page 56 of 70 . 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.

Choose Save.1 Use The purpose of this activity is to define actions used in warranty processing. choose New Entries. 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.10 Defining Control Data 3. Maintain the following data: Page 57 of 70 . On the initial screen.10. Defining Actions Procedure 1. 3. 3.Warranty Processing_Pre Credit_ConfigGuide 5.

IC-Version for sending YA65 YA66 Y_WTY04_ VER_IC_SE ND YA10: Page 58 of 70 . YA66. A043 YA50 YA62 Post goods receipt to Qstock Split Groups Proposal With Dialog Box Rel. A008 YA65.GR & Version to Reimburser 3rd step .Warranty Processing_Pre Credit_ConfigGuide 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 . A070 Function Module Action Sequence YA11 YA12 YA13.To Claimant & Debit Memo Post Complete Claim WTY04_CL AIM_CLOS E Y_WTY04_ GR_QSTOC K T061. T810. A040.Check WTY & Credit Memo Post 2nd step . T062 A200.

Warranty Processing_Pre Credit_ConfigGuide YA11: YA12: Page 59 of 70 .

Warranty Processing_Pre Credit_ConfigGuide YA50: YA62: YA65: Page 60 of 70 .

10. Result The actions are defined.2 Use Defining Action Controls The purpose of this activity is to define action controls. Choose Save.Warranty Processing_Pre Credit_ConfigGuide YA66: 4. 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 . 3.

and on the Change View “Action Matrix”: Overview Screen. Choose Enter. 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 .Warranty Processing_Pre Credit_ConfigGuide 2. Double-click Action Matrix. On the New Entries: Details of Added Entries Screen. On the initial screen. maintain the following records: Field name Action Control Action Control Description User action and values YA10 Processor Actions Note 4. choose New Entries. 5. 3.

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 . 7. Choose Save.Warranty Processing_Pre Credit_ConfigGuide 6.

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 .Warranty Processing_Pre Credit_ConfigGuide Result The action controls are defined. Action Function Entry in Command fld. Procedure 1. choose New Entries and enter the following data: Field name Function Entry in Command fld. Action Function Entry in Command fld. On the “Change View: Assign Function Code to Action Code “ Overview screen. 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. Action Function Entry in Command fld.10.3 Use Assigning Function Codes to Action Codes The purpose of this activity is to assign the function code to the action code. Action Function Entry in Command fld. 3.

Choose Save. Choose Save.4 Use Defining Copy Procedure The purpose of this activity is to create the copying control. Procedure Page 65 of 70 . On the New Entries: Overview of Added Entries Screen.10. maintain the following data: Field name Copy Procedure Description of Copy Procedure Description User action and values Y1 BP Standard Note 4. 3. 3. 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.10. 3. Procedure 1.Warranty Processing_Pre Credit_ConfigGuide 3.5 Use Assigning Copy Procedure to Claim Type The purpose of this activity is to assign copy procedure to claim type.

1 Use The purpose of this activity is to create the pushbutton on the warranty claim screen. choose New Entries. Defining Pushbutton Profile Procedure 1. 3.11. 3. 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. 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. 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 . On the New Entries: Overview of Added Entries screen.11 Layout Settings 3.Warranty Processing_Pre Credit_ConfigGuide 1. On the initial screen.

1. 3.Warranty Processing_Pre Credit_ConfigGuide 2. 3. choose New Entries.11. choose New Entries. On the Change View “Action Control” Overview screen. Choose Save.1 Use Assigning Action Controlling The purpose of this activity is to assign the action controls to the pushbutton profile. On the New Entries: Overview of Added Entries screen. On the initial screen. maintain the following data: Pushbutton Profile YA_PROFILE Profile Description BP Auto for Processor Action Control YA10 4. On the initial screen. Access the activity using one of the following navigation options: Transaction Code IMG Menu OWTY Warranty Claim Processing → Layout → Define Pushbutton Profiles 2. select the pushbutton profile you created in the previous step and double click Action Control. 3. 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 . Procedure 1.

To Claimant Page 68 of 70 . On the initial screen. select the pushbutton profile you created in the previous step and double click Actions. choose New Entries. On the Change View “Actions”: Overview Screen. Access the activity using one of the following navigation options: Transaction Code IMG Menu OWTY Warranty Claim Processing → Layout → Define Pushbutton Profiles 2. 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. 3.Assigning Action Code The purpose of this activity is to assign the actions to the pushbutton profile. Choose Enter.11. Choose Save 3.1. 5. Procedure 1.2 Use Defining Pushbutton Profile .Warranty Processing_Pre Credit_ConfigGuide 4.

Warranty Processing_Pre Credit_ConfigGuide 4. 3.3 Use Defining Message Groups The purpose of this activity is to define message groups. 3. choose New Entries. Choose Save. Access the activity using one of the following navigation options: Transaction Code IMG Menu OWTY Warranty Claim Processing → Layout → Define Message Groups 2.11.1. Choose Enter. maintain the following data: Message Group KL YAGR Description Delivery w/o Charge Goods receipt into Q-Stock Page 69 of 70 . Result The pushbutton profile is created. On the initial screen. 5. Procedure 1. On the New Entries: Details of Added Entries Screen.

Page 70 of 70 . 3.Warranty Processing_Pre Credit_ConfigGuide 4. choose New Entries. Result Warranty document type determination is defined.1 Use The purpose of this activity is to maintain document type determination. 4. 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.12. On the Change View “Document Type Determination for Warranty”: Overview screen. Result Message Groups YAGR and KL are created. Access the activity using one of the following navigation options: Transaction Code YWTY_DM 2.12 Manual Step 3. Choose Save. Choose Enter to confirm your entries. Choose Save. Maintaining Document Type Determination for Warranty Procedure 1.

Sign up to vote on this title
UsefulNot useful