AFS Tables
J_3ABSSI AFS Stock (Sizes)
J_3AGDCTP1 AFS Grid Value Conversion Types
J_3ADCONV AFS Grid Dimension Conversion
J_3AGDCTPT AFS: Size Conversion Types Texts
J_3AGDCTV2 Define Conversion ( VIEW )
J_3AVBFAD Document Flow - Dynamic Part: AFS Enhancement ( Structure )
Characteristics :
CABN Characteristics ( o.a. batch/vendor)
CABNT Characteristics description
CAWN Characteristics ( o.a. material)
CAWNT Characteristics description
AUSP Characteristic Values
Tuesday, November 24, 2009
Implementing Feature of Automatic De-allocation of Stock for Transfer Posting Movement in AFS 6.0
Implementing Feature of Automatic De-allocation of Stock for Transfer Posting Movement in AFS 6.0
Applies to:
The process applies to the SAP industry solution for Apparel and Footwear release AFS 6.0.
For more information, visit the Enterprise Resource Planning homepage.
Summary
AFS Allocation Run (ARUN) module fix reserves stock on a batch in the inventory. When the AFS article has suspected quality issues it becomes necessary to move the stock from valuated un-restricted use to quality inspection in the batch stock segment. But since the stock was fixed, it became impossible to move it to quality inspection segment until the fix was manually revoked via the ARUN management tool.
With the newly implemented feature in AFS 6.0 the stock can be automatically de-allocated for specific transfer posting movement types.
Author: Raghu Hiremaglur
Company: Infosys Technologies Ltd., Bangalore INDIA.
Created on: 25 February 2009
Author Bio
Raghu Hiremaglur has over nine years of consulting experience in ERP Materials Management (MM) and Warehouse Management (WM) modules which includes the last eight years in SAP MM and WM. He has extensive expertise in the industry specific Apparel and Footwear (IS-AFS) business domain and has been working in this domain over the past seven years.
He currently works as an SAP Consultant in the Enterprise Solutions department at Infosys Technologies Ltd.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 1
Implementing Feature of Automatic De-allocation of Stock for Transfer Posting Movement in AFS 6.0
Table of Contents
Functional Background......................................................................................................................................3
Client’s Requirement Realization......................................................................................................................3
Client’s Enhancement in AFS 6.0...................................................................................................................3
Conclusion.........................................................................................................................................................4
Technical Impact................................................................................................................................................4
Result.................................................................................................................................................................5
Related Content.................................................................................................................................................5
Disclaimer and Liability Notice...........................................................................................................................6
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 2
Implementing Feature of Automatic De-allocation of Stock for Transfer Posting Movement in AFS 6.0
Functional Background
The client is an Apparel and Footwear major based in Germany and the project was upgrading the SAP AFS infrastructure from release AFS 3.0B to AFS 6.0
Transfer posting Movement 322 is a SAP standard movement to transfer stock from Valuated Unrestricted-use to Quality Inspection in the batch stock segment.
The client’s North American subsidiary uses this movement in most cases when the article has suspected quality issues or when it should undergo a material change (from specific to generic style or from category A to category B), or when the article is lost in a cycle count and is expected to be found again.
When there exists fixed/reserved stock for a batch the client, wanted the feature of automatic de-allocation in a situation when the MRP relevant stock is falling below the AFS fixed/reserved quantity as a result of the 322 posting. In AFS 3.0B release, by BDC technique the stock was first de-allocated and later the movement was done.
From AFS 6.0 release, the feature of automatic de-allocation was provided as a standard feature by SAP AFS but this feature was only for goods issue postings.
Client’s Requirement Realization
Client’s Enhancement in AFS 6.0
An additional node was introduced in ARUN customizing (transaction J3AS) to make configuration settings also for transfer posting movements to handle automatic de-allocation.
A new node was created under AFS Allocation Run -> Cross Applications -> Transfer Posting handling. Under this another new node was created to hold transfer posting movement types for which the client wanted the de-allocation functionality.
With this setting, for transfer posting movements which have a “Goods issue” attribute (table T156-SHKZG = ‘H’), the standard AFS logic itself handled the feature of automatic de-allocation. (For example for movement types 309, …)
However, movement type 322 has setting T156-SHKZG = ‘S’. There is no standard SAP AFS logic to handle automatic de-allocation for such transfer posting movements.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 3
Implementing Feature of Automatic De-allocation of Stock for Transfer Posting Movement in AFS 6.0
Conclusion
Hence, the author and consultant responsible for this business process realization suggested the client to go in for an AFS logic modification to cater this business requirement besides the created customer specific node in IMG.
Technical Impact
In AFS 6.0 release, the form routine J_3A_RESM_PRUEFEN_UMLAG of program SAPMM07M is designed to check that MRP relevant stock does not fall below the allocated quantity in case of different transfer posting movements. This is the SAP standard logic.
The proposed suggestion was to implement an enhanced logic in that form routine such that the above mentioned settings are considered and instead of error message being displayed when the MRP relevant stock is not sufficient then the ARUN function module /AFS/ARUN_CA_MBXX_HANDLING which handles the de-allocation needs to be called.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 4
Implementing Feature of Automatic De-allocation of Stock for Transfer Posting Movement in AFS 6.0
Result
This was successfully implemented and facilitated the client to enormously reduce costs, effort and time in changing many of the critical interfaces it runs from 3-party (non-SAP) warehouse management systems to SAP AFS 6.0.
Related Content
For more information, visit the Business Process Expert homepage.
For more information, visit the Enterprise Resource Planning homepage.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 5
Implementing Feature of Automatic De-allocation of Stock for Transfer Posting Movement in AFS 6.0
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 6
Disclaimer and Liability Notice
This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.
Applies to:
The process applies to the SAP industry solution for Apparel and Footwear release AFS 6.0.
For more information, visit the Enterprise Resource Planning homepage.
Summary
AFS Allocation Run (ARUN) module fix reserves stock on a batch in the inventory. When the AFS article has suspected quality issues it becomes necessary to move the stock from valuated un-restricted use to quality inspection in the batch stock segment. But since the stock was fixed, it became impossible to move it to quality inspection segment until the fix was manually revoked via the ARUN management tool.
With the newly implemented feature in AFS 6.0 the stock can be automatically de-allocated for specific transfer posting movement types.
Author: Raghu Hiremaglur
Company: Infosys Technologies Ltd., Bangalore INDIA.
Created on: 25 February 2009
Author Bio
Raghu Hiremaglur has over nine years of consulting experience in ERP Materials Management (MM) and Warehouse Management (WM) modules which includes the last eight years in SAP MM and WM. He has extensive expertise in the industry specific Apparel and Footwear (IS-AFS) business domain and has been working in this domain over the past seven years.
He currently works as an SAP Consultant in the Enterprise Solutions department at Infosys Technologies Ltd.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 1
Implementing Feature of Automatic De-allocation of Stock for Transfer Posting Movement in AFS 6.0
Table of Contents
Functional Background......................................................................................................................................3
Client’s Requirement Realization......................................................................................................................3
Client’s Enhancement in AFS 6.0...................................................................................................................3
Conclusion.........................................................................................................................................................4
Technical Impact................................................................................................................................................4
Result.................................................................................................................................................................5
Related Content.................................................................................................................................................5
Disclaimer and Liability Notice...........................................................................................................................6
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 2
Implementing Feature of Automatic De-allocation of Stock for Transfer Posting Movement in AFS 6.0
Functional Background
The client is an Apparel and Footwear major based in Germany and the project was upgrading the SAP AFS infrastructure from release AFS 3.0B to AFS 6.0
Transfer posting Movement 322 is a SAP standard movement to transfer stock from Valuated Unrestricted-use to Quality Inspection in the batch stock segment.
The client’s North American subsidiary uses this movement in most cases when the article has suspected quality issues or when it should undergo a material change (from specific to generic style or from category A to category B), or when the article is lost in a cycle count and is expected to be found again.
When there exists fixed/reserved stock for a batch the client, wanted the feature of automatic de-allocation in a situation when the MRP relevant stock is falling below the AFS fixed/reserved quantity as a result of the 322 posting. In AFS 3.0B release, by BDC technique the stock was first de-allocated and later the movement was done.
From AFS 6.0 release, the feature of automatic de-allocation was provided as a standard feature by SAP AFS but this feature was only for goods issue postings.
Client’s Requirement Realization
Client’s Enhancement in AFS 6.0
An additional node was introduced in ARUN customizing (transaction J3AS) to make configuration settings also for transfer posting movements to handle automatic de-allocation.
A new node was created under AFS Allocation Run -> Cross Applications -> Transfer Posting handling. Under this another new node was created to hold transfer posting movement types for which the client wanted the de-allocation functionality.
With this setting, for transfer posting movements which have a “Goods issue” attribute (table T156-SHKZG = ‘H’), the standard AFS logic itself handled the feature of automatic de-allocation. (For example for movement types 309, …)
However, movement type 322 has setting T156-SHKZG = ‘S’. There is no standard SAP AFS logic to handle automatic de-allocation for such transfer posting movements.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 3
Implementing Feature of Automatic De-allocation of Stock for Transfer Posting Movement in AFS 6.0
Conclusion
Hence, the author and consultant responsible for this business process realization suggested the client to go in for an AFS logic modification to cater this business requirement besides the created customer specific node in IMG.
Technical Impact
In AFS 6.0 release, the form routine J_3A_RESM_PRUEFEN_UMLAG of program SAPMM07M is designed to check that MRP relevant stock does not fall below the allocated quantity in case of different transfer posting movements. This is the SAP standard logic.
The proposed suggestion was to implement an enhanced logic in that form routine such that the above mentioned settings are considered and instead of error message being displayed when the MRP relevant stock is not sufficient then the ARUN function module /AFS/ARUN_CA_MBXX_HANDLING which handles the de-allocation needs to be called.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 4
Implementing Feature of Automatic De-allocation of Stock for Transfer Posting Movement in AFS 6.0
Result
This was successfully implemented and facilitated the client to enormously reduce costs, effort and time in changing many of the critical interfaces it runs from 3-party (non-SAP) warehouse management systems to SAP AFS 6.0.
Related Content
For more information, visit the Business Process Expert homepage.
For more information, visit the Enterprise Resource Planning homepage.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 5
Implementing Feature of Automatic De-allocation of Stock for Transfer Posting Movement in AFS 6.0
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 6
Disclaimer and Liability Notice
This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.
Program to get the User exit for any Transaction Code
Program to get the User exit for any Transaction Code
REPORT zuser_exit NO STANDARD PAGE HEADING.
TABLES : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
TABLES : tstct.
DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
DATA : field1(30).
DATA : v_devclass LIKE tadir-devclass.
PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.
SELECT SINGLE * FROM tstc WHERE tcode EQ p_tcode.
IF sy-subrc EQ 0.
SELECT SINGLE * FROM tadir WHERE pgmid = ‘R3TR’
AND object = ‘PROG’
AND obj_name = tstc-pgmna.
MOVE : tadir-devclass TO v_devclass.
IF sy-subrc NE 0.
SELECT SINGLE * FROM trdir WHERE name = tstc-pgmna.
IF trdir-subc EQ ‘F’.
SELECT SINGLE * FROM tfdir WHERE pname = tstc-pgmna.
SELECT SINGLE * FROM enlfdir WHERE funcname =
tfdir-funcname.
SELECT SINGLE * FROM tadir WHERE pgmid = ‘R3TR’
AND object = ‘FUGR’
AND obj_name EQ enlfdir-area.
MOVE : tadir-devclass TO v_devclass.
ENDIF.
ENDIF.
SELECT * FROM tadir INTO TABLE jtab
WHERE pgmid = ‘R3TR’
AND object = ‘SMOD’
AND devclass = v_devclass.
SELECT SINGLE * FROM tstct WHERE sprsl EQ sy-langu AND
tcode EQ p_tcode.
FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
WRITE:/(19) ‘Transaction Code - ‘,
20(20) p_tcode,
45(50) tstct-ttext.
SKIP.
IF NOT jtab[] IS INITIAL.
WRITE:/(95) sy-uline.
FORMAT COLOR COL_HEADING INTENSIFIED ON.
WRITE:/1 sy-vline,
2 ‘Exit Name’,
21 sy-vline ,
22 ‘Description’,
95 sy-vline.
WRITE:/(95) sy-uline.
LOOP AT jtab.
SELECT SINGLE * FROM modsapt
WHERE sprsl = sy-langu AND
name = jtab-obj_name.
FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
WRITE:/1 sy-vline,
2 jtab-obj_name HOTSPOT ON,
21 sy-vline ,
22 modsapt-modtext,
95 sy-vline.
ENDLOOP.
WRITE:/(95) sy-uline.
DESCRIBE TABLE jtab.
SKIP.
FORMAT COLOR COL_TOTAL INTENSIFIED ON.
WRITE:/ ‘No of Exits:’ , sy-tfill.
ELSE.
FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
WRITE:/(95) ‘No User Exit exists’.
ENDIF.
ELSE.
FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
WRITE:/(95) ‘Transaction Code Does Not Exist’.
ENDIF.
AT LINE-SELECTION.
GET CURSOR FIELD field1.
CHECK field1(4) EQ ‘JTAB’.
SET PARAMETER ID ‘MON’ FIELD sy-lisel+1(10).
CALL TRANSACTION ‘SMOD’ AND SKIP FIRST SCREEN.
REPORT zuser_exit NO STANDARD PAGE HEADING.
TABLES : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
TABLES : tstct.
DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
DATA : field1(30).
DATA : v_devclass LIKE tadir-devclass.
PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.
SELECT SINGLE * FROM tstc WHERE tcode EQ p_tcode.
IF sy-subrc EQ 0.
SELECT SINGLE * FROM tadir WHERE pgmid = ‘R3TR’
AND object = ‘PROG’
AND obj_name = tstc-pgmna.
MOVE : tadir-devclass TO v_devclass.
IF sy-subrc NE 0.
SELECT SINGLE * FROM trdir WHERE name = tstc-pgmna.
IF trdir-subc EQ ‘F’.
SELECT SINGLE * FROM tfdir WHERE pname = tstc-pgmna.
SELECT SINGLE * FROM enlfdir WHERE funcname =
tfdir-funcname.
SELECT SINGLE * FROM tadir WHERE pgmid = ‘R3TR’
AND object = ‘FUGR’
AND obj_name EQ enlfdir-area.
MOVE : tadir-devclass TO v_devclass.
ENDIF.
ENDIF.
SELECT * FROM tadir INTO TABLE jtab
WHERE pgmid = ‘R3TR’
AND object = ‘SMOD’
AND devclass = v_devclass.
SELECT SINGLE * FROM tstct WHERE sprsl EQ sy-langu AND
tcode EQ p_tcode.
FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
WRITE:/(19) ‘Transaction Code - ‘,
20(20) p_tcode,
45(50) tstct-ttext.
SKIP.
IF NOT jtab[] IS INITIAL.
WRITE:/(95) sy-uline.
FORMAT COLOR COL_HEADING INTENSIFIED ON.
WRITE:/1 sy-vline,
2 ‘Exit Name’,
21 sy-vline ,
22 ‘Description’,
95 sy-vline.
WRITE:/(95) sy-uline.
LOOP AT jtab.
SELECT SINGLE * FROM modsapt
WHERE sprsl = sy-langu AND
name = jtab-obj_name.
FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
WRITE:/1 sy-vline,
2 jtab-obj_name HOTSPOT ON,
21 sy-vline ,
22 modsapt-modtext,
95 sy-vline.
ENDLOOP.
WRITE:/(95) sy-uline.
DESCRIBE TABLE jtab.
SKIP.
FORMAT COLOR COL_TOTAL INTENSIFIED ON.
WRITE:/ ‘No of Exits:’ , sy-tfill.
ELSE.
FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
WRITE:/(95) ‘No User Exit exists’.
ENDIF.
ELSE.
FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
WRITE:/(95) ‘Transaction Code Does Not Exist’.
ENDIF.
AT LINE-SELECTION.
GET CURSOR FIELD field1.
CHECK field1(4) EQ ‘JTAB’.
SET PARAMETER ID ‘MON’ FIELD sy-lisel+1(10).
CALL TRANSACTION ‘SMOD’ AND SKIP FIRST SCREEN.
AFS Transaction codes
AFS Transaction codes
/AFS/J5AI Source Allocation Schedule II
/AFS/LIEF_CHECK Delivery Check Report
/AFS/MCC AFS Mass Customer Change
/AFS/MCTE AFS SD Standard Analysis
/AFS/MD02 AFS-MRP: Single-item Planning
/AFS/MD04 AFS Stock/Requirements List
/AFS/MD06 AFS MRP List
/AFS/MD09 AFS Pegged Requirements
/AFS/MD4C AFS Order Report
/AFS/MDC Mass Data Change of Documents
/AFS/ME2A AFS Confirmation report
/AFS/MMCUST C MM customer-specific messages AFS
/AFS/MM_MP MM Missing Parts Lists- Subcontracti
/AFS/MRPBROWSER MRP Browser
/AFS/MRP_CR_STARTER Check Report Starter
/AFS/MRP_S430 AFS Quantity and Distribution Tool
/AFS/MSC2 Batch Revaluation
/AFS/MSOEX AFS MSO order explosion/log
/AFS/NDIF_CHANGECOVS Categ. Structure or Coverage Strat.
/AFS/NDIF_MAP_CONV Convert Dims to Characteristics
/AFS/NDIF_MASS_REORG Mass Deletion of AFS Config. Data
/AFS/NDIF_MASS_UPD New Dimension Mass Update
/AFS/NDIF_MAT_CLASS NDIF: create material class
/AFS/NDIF_MAT_UPD Mass Update Report
/AFS/NDIF_RUNTIME Mass Update – Run-time Versions
/AFS/NDIF_SET_CONF Set Configuration Indicator
/AFS/NDIF_SKU_VAR NDIF: create sku variant
/AFS/PIRMI Interface Flex.Planning / AFS
/AFS/PP01 Maintain qty distribution rule grid
/AFS/PP012 Check Quantity Distr. Rule Grid
/AFS/PRPK_DIST SD Quantity Distribution
/AFS/RS02 Maintain AFS Requirement Seasons
/AFS/RS03 Display AFS Requirement Seasons
/AFS/SA01 Cap Mass Data Changes I – Capacity
/AFS/SA02 trans for mass cap change dialog
/AFS/SA03 AFS Vendor Capacity Situation Report
/AFS/SA04 Capacity reduction after simulation
/AFS/SA05 Report for not assigned p.r.
/AFS/SEAS_TABLE_DISP AFS Display Season Condition Tables
/AFS/SPLITPO Change & Split PO, PO confirmation
/AFS/SS02 Maintain AFS Stock Seasons
/AFS/SS03 Display AFS Stock Seasons
/AFS/SSET_DISP Display AFS ARun Selection Set
/AFS/SSET_REORG Reorganize Selection Sets
/AFS/SUB_RULE ATP Substitution Rule
/AFS/SUB_T685_TS Assignment Text/Condition Type
/AFS/SUB_TVSU_V Substitution: ATP Locks
/AFS/SUB_TYPE Customizing Substitution Type
/AFS/T681F_JM Field Catalog Grid Determination MM
/AFS/T681F_JV Field Catalog Grid Determination SD
/AFS/T681F_KV Field Catalog Value-Added Service SD
/AFS/T681F_LV Field Catalog Season SD
/AFS/TAB_GENERATION ARun table generation
/AFS/TVAG Maint.Reasons for Rejection for AFS
/AFS/V_R2 AFS Rescheduling – analyse
/AFS/V_RA Back Order List
/AFS/WWW_PO_CONF Confirmation of Work Progress
/AFS/J5AI Source Allocation Schedule II
/AFS/LIEF_CHECK Delivery Check Report
/AFS/MCC AFS Mass Customer Change
/AFS/MCTE AFS SD Standard Analysis
/AFS/MD02 AFS-MRP: Single-item Planning
/AFS/MD04 AFS Stock/Requirements List
/AFS/MD06 AFS MRP List
/AFS/MD09 AFS Pegged Requirements
/AFS/MD4C AFS Order Report
/AFS/MDC Mass Data Change of Documents
/AFS/ME2A AFS Confirmation report
/AFS/MMCUST C MM customer-specific messages AFS
/AFS/MM_MP MM Missing Parts Lists- Subcontracti
/AFS/MRPBROWSER MRP Browser
/AFS/MRP_CR_STARTER Check Report Starter
/AFS/MRP_S430 AFS Quantity and Distribution Tool
/AFS/MSC2 Batch Revaluation
/AFS/MSOEX AFS MSO order explosion/log
/AFS/NDIF_CHANGECOVS Categ. Structure or Coverage Strat.
/AFS/NDIF_MAP_CONV Convert Dims to Characteristics
/AFS/NDIF_MASS_REORG Mass Deletion of AFS Config. Data
/AFS/NDIF_MASS_UPD New Dimension Mass Update
/AFS/NDIF_MAT_CLASS NDIF: create material class
/AFS/NDIF_MAT_UPD Mass Update Report
/AFS/NDIF_RUNTIME Mass Update – Run-time Versions
/AFS/NDIF_SET_CONF Set Configuration Indicator
/AFS/NDIF_SKU_VAR NDIF: create sku variant
/AFS/PIRMI Interface Flex.Planning / AFS
/AFS/PP01 Maintain qty distribution rule grid
/AFS/PP012 Check Quantity Distr. Rule Grid
/AFS/PRPK_DIST SD Quantity Distribution
/AFS/RS02 Maintain AFS Requirement Seasons
/AFS/RS03 Display AFS Requirement Seasons
/AFS/SA01 Cap Mass Data Changes I – Capacity
/AFS/SA02 trans for mass cap change dialog
/AFS/SA03 AFS Vendor Capacity Situation Report
/AFS/SA04 Capacity reduction after simulation
/AFS/SA05 Report for not assigned p.r.
/AFS/SEAS_TABLE_DISP AFS Display Season Condition Tables
/AFS/SPLITPO Change & Split PO, PO confirmation
/AFS/SS02 Maintain AFS Stock Seasons
/AFS/SS03 Display AFS Stock Seasons
/AFS/SSET_DISP Display AFS ARun Selection Set
/AFS/SSET_REORG Reorganize Selection Sets
/AFS/SUB_RULE ATP Substitution Rule
/AFS/SUB_T685_TS Assignment Text/Condition Type
/AFS/SUB_TVSU_V Substitution: ATP Locks
/AFS/SUB_TYPE Customizing Substitution Type
/AFS/T681F_JM Field Catalog Grid Determination MM
/AFS/T681F_JV Field Catalog Grid Determination SD
/AFS/T681F_KV Field Catalog Value-Added Service SD
/AFS/T681F_LV Field Catalog Season SD
/AFS/TAB_GENERATION ARun table generation
/AFS/TVAG Maint.Reasons for Rejection for AFS
/AFS/V_R2 AFS Rescheduling – analyse
/AFS/V_RA Back Order List
/AFS/WWW_PO_CONF Confirmation of Work Progress
Subscribe to:
Posts (Atom)