Maintain Product Segmentation
Application component: Segmentation related data maintenance
App type: SAP GUI
Key features: Using SGT_SETUP transaction you can leverage the following features: Segmentation Structure A segmentation structure is a well-defined sequential combination of segmentation characteristics. When you create a segmentation structure, it is in unlocked state until a segmentation strategy is assigned to it. Once a segmentation strategy is created for the segmentation structure, it is moved to locked state. A segmentation structure can have multiple segmentation strategies but vice versa is not possible. When you copy a segmentation structure, then the characteristics are copied to the new segmentation structure.  Segmentation Strategy A segmentation strategy determines how requirement segments are assigned to stock segments.  You can scope a segmentation strategy to define the mapping rules or segment combinations in a segmentation strategy. Scope can be one of the following: Scope 1: If the scope is set as 1, then both requirement segment and stock segment are considered during determinations. Scope 2: If the scope is set as 2, then only requirement segment is considered during determinations. Stock segment is not considered.   When you create a segmentation strategy to a segmentation structure, the nodes are automatically created with yellow traffic lights. Once the system generated the rules, the traffic lights are changed to green. Any change to the segment values, changes the traffic light back to yellow. You can copy a segmentation strategy to another segmentation strategy only when it belongs to the same structure. While copying one segmentation strategy to another, you can choose an option Generate Rules to copy all the rules of the node at once.  You can delete a segmentation strategy only if it is not used by any material and no open documents use that particular segmentation strategy.Note You can delete segmentation values for segmentation combinations. However, if you want to delete multiple segmentation values, you can use the transaction SE38 to execute the report program SGT_DELETE_CATS. You can assign segmentation strategy directly to a non-segmented article provided no open documents exists for that article.  Segmentation Combinations When you select Generate Segment combinations , all the characteristic of the segmentation structure are displayed. For each characteristic, you must select the segments. Once the segments are selected, the segment combinations get generated based on them.  Maintenance of Rules  ARun/MRP: Requirement/Stock Allocation: Use this node to maintain stock and requirement segments for a particular strategy at ARun/MRP node level. You can specify how the requirement segments use the stock segments during the material requirements planning run. The system considers the available stock and the future receipts. You can assign the same stock segment to several requirement segments and vice versa.This node supports the following mappings and the matching rules:  Rules Mapping Matching Rules Supported (Yes/No)    1.1 Yes (* to*)   N:1 Yes (* to 1)   1:N Yes (1 to *)   N:M Yes (* to #)  You can generate rules at ARUN/MRP: Requirement/Stock Allocation node for the corresponding strategy. When the rules are generated, following traffic lights are displayed: Yellow: (Warning) indicates that the system could not generate the rules.  Green: (Success) indicates that system has generated all the rules.  ATP: Define Pool Segment and Check Level: Use this node to maintain valid requirement segments for ATP. You can specify how the segment pools can be checked during the availability check. The system considers the available stock and the future receipts. For each pool, you can specify the check level of segment values during ATP. You cannot maintain same segment in different pools.  Rules Mapping Matching Rules Supported (Yes/No)    1.1 Yes (*)   M:M Yes  If there is a change in the segment check level for a pool, then all the segment check level values belonging to that particular pool must be updated with the latest value. System cannot generate rules for this particular node. Dependent Requirements/Stock Transfer: Use this to maintain stock segments and requirement segments for Dependent Requirements/Stock transfer node level. You can define the assignment of stock segments to requirements segments. Use this setting when a stock transfer is created between two plants, and when the dependent requirement is generated.  Rules Mapping Matching Rules Supported (Yes/No)    1:1 Yes (* to*)   N:1 Yes (* to 1)   1:N No (1 to *)   N:M No (* to #)  You can generate rules at Dependent Requirements/Stock Transfer node for the corresponding strategy. When the rules are generated, following traffic lights are displayed: Yellow: (Warning) indicates that system could not generate the rules.  Green: (Success) indicates that the system has generated all the rules.  Requirement to Stock Conversion: Use this to maintain stock segments and requirement segments for Requirement to Stock Conversion node level. You can define the stock segment to be proposed for a specific requirement when the system creates proposals during the lot-size calculation.   Rules Mapping Matching Rules Supported (Yes/No)    1:1 Yes (* to*)   N:1 Yes (* to 1)   1:N No (1 to *)   N:M No (* to #)  You can generate rules at Requirement to Stock Conversion node for the corresponding strategy. When the system generates the rules, following traffic lights are displayed: Yellow: (Warning) indicates that the system could not generate the rules.  Green: (Success) indicates that the system has generated all the rules.  Planned Independent Requirements Consumption: Use this to maintain stock segments and requirement segments for Planned Independent Requirements Consumption node level. You can define the requirement segments of the planned independent requirements (PIR) and the requirements segments of the customer requirement that consumes the requirement segments of the PIR.  Rules Mapping Matching Rules Supported (Yes/No)    1:1 Yes (* to*)   N:1 Yes (* to 1)   1:N Yes (1 to *)   N:M Yes (* to #)  You can generate rules at Requirement to Stock Conversion node for the corresponding strategy. When system generates the rules, following traffic lights are displayed: Yellow: (Warning) indicates that system could not generate the rules.  Green: (Success) indicates that system has generated all the rules.    Default Segmentation Use Default Segmentation to maintain the default segmentation value for a particular segmentation strategy which gets determined during consumption of material in applications.  Display Rules Use Display Rules to display rules for particular strategy available in the database either at strategy level or at the node level, and not at structure level. The same functionality is also provided by the Display Consolidated Segmentation Rules (SGT_DISPLAY_RULES) report.  Generate Rules Use Generate Rules to generate the rules either at segmentation strategy level or at node level.  When the rules are generated for a particular node, the traffic light against the node turns green. If the rules are maintained at all the nodes and you generate rules at strategy level, then the traffic for all node related to that particular strategy node turns green. If you change the rules at any node, the traffic light turns yellow. If any of the nodes contains traffic light as yellow, then the segmentation strategy has traffic light as yellow in the ALV tree.  The same functionality is also provided by the Generate Consolidated Segmentation Rules (SGT_GENERATE_RULES) report.  Upload/Download Use Upload/Download to upload or download the segmentation strategy to or from a system. You can upload a segmentation strategy provided the characteristics already exist in the system.  Material Assignment For a material or an article, you can   Assign segmentation structure or segmentation strategy at client (basic data) level.   Assign segmentation strategy at plant level.   Unassign segmentation details at both client and plant levels, that is, the segmentation details are removed at both client and plant levels at once.   Note  Multiple users can use SGT_SETUP transaction for different segmentation structures and strategies at the same time. However, you can lock or edit one segmentation structure and strategy at a time. You can navigate from this report to a material (transaction MM03), or an article (transaction MM43), or a characteristic (transaction CT04), if you have the required authorizations. 
Business roles: Master Data Specialist - Product Data (Retail)