Object Determination Softproviding Core User Documentation

Transcription

1 Great ideas are always simple Softproviding simply makes them happen. Object Determination Softproviding Core User Documentation

2 Version: 1.00 Date 28. June 2017 Release: v2.50 Softproviding AG Riehenring 175 CH-4058 Basel Switzerland +41 (0) SAP + Softproviding + YOU. Leading the field.

3 Contents 1 Overview 4 2 Customizing SAP Standard Class Type Maintain Object Table Create Class Type Maintain Class Type Softproviding Core Classes Objects Output Fields Interface Fields 17 3 Application Master Data Class Administration Characteristics Administration Plan Management General Overview Display Object Plan Change Object Plan Individual Plan Editing for the Effective Date Display Object Plan Change Object Plan Program Interfaces Object Determination Calls BAdIs Authorizations 34 4 Technology Comparison: Object Determination vs. Determination Application Assignment of the Corresponding Determination Application Elements Comparison of Elements Conclusion 39 3/39

4 1 Overview An SAP classification system is used as the basis for object determination. A classification system describes any kind of object by using characteristics. Similar objects are consolidated into classes. Object determination consists of the following areas: Classification Definition of characteristics within a class Object definition Formation of groups with different characteristics The stated terminology is based on the stock placement strategy for a strip storage: Classification Class: Pig half Characteristics: Slaughtering weight Lean meat content Object determination Storage group 1 Slaughtering weight: 90 <-> 120 Kg Lean meat content: 40 <-> 44 % Storage group 2 Slaughtering weight: 72 <-> 130 Kg Lean meat content: 55 <-> 59 % Storage group 3 Slaughtering weight: 100 <-> 110 Kg Lean meat content: > 60 % Each storage group represents a particular area (= strips) of the cold-store, e.g. Storage group 1 = Strip 1 10 Storage group 2 = Strip Storage group 3 = Strip To enable completion of inventory management in SAP, a material number is required instead of the storage group. The material number is ascertained by means of object determination: Storage group 1 = Mat. No Storage group 2 = Mat. No Storage group 3 = Mat. No Object Determination Softproviding Core User Documentation 4/39

5 2 Customizing Object Determination Softproviding Core User Documentation 5/39

6 2.1 SAP Standard Class Type Overview The Softproviding object determination classification model uses the SAP standard classification system. The SAP standard classification system customizing setting is not covered in this document. Please refer to the relevant SAP standard documentation for a detailed description of the classification system. Prerequisites The SAP user has access authorization for the SAP customizing implementation guide and the authorization to create customizing transport orders. Procedure IMG menu Cross-Application Components > Classification System > Classes > Maintain Object Types and Class Types 1. Call up the stated customizing table to maintain the class type Maintain Object Table 2. Select Object table in the menu tree. 3. Click the New Entries button. The following fields and flags are available to you to enter data for each new Object Table object. Fields and flags for the object Object Table Table Table text Screen No. for CL20N CL24N New Object CL24N New Object CL24N Header Line Screen No. value Database table for the master record that can also be linked to an object link. of the table that contains objects that can be classified. Dynpro number for screen components for transaction CL20N Dynpro number for screen components for transaction CL24N Dynpro number for screen components for transaction CL24N Dynpro number for screen components in the classification pool Object Determination Softproviding Core User Documentation 6/39

7 Keywords Characteristics screen Documents Texts Standards data Two-line basic screen If this field is checked, the keyword screen is displayed when maintaining and displaying the class. If this field is checked, the characteristics screen is displayed in the screen sequence when maintaining and displaying the class. Flag specifying whether the documents screen should appear in the screen sequence for a class type when maintaining and displaying the class. If this field is checked, the text screen is displayed when maintaining and displaying the class. If this field is checked, the standards data screen is displayed in the screen sequence when maintaining and displaying the class. CL20 access: one/two-line screen component Example Table Table text Screen No. for CL20N CL24N New Object CL24N New Object CL24N Header Line Screen No. value Keywords Characteristics screen Documents Texts Standards data Two-line basic screen /SPMEAT/LAGGR Storage group master table X X X 4. Click the Save button to save your entries. The warning message "Please select the key from the permitted name space" can be ignored Create Class Type 1. Select the /SPMEAT/LAGGR entry in the customizing table. 2. Click on Class Types in the menu tree. Object Determination Softproviding Core User Documentation 7/39

8 3. Click the New Entries button. The following fields and flags are available to you to enter data for each new Class Type object. Fields and flags for the object Class type Class type Name of class type Name of the object database table Screen keywords Characteristics screen Screen documents Screen texts Screen standards Change service (time validity) for classification Change service (parameter validity) for classification Change documents classification Flag multiple classifications Classification only permitted via master record Only variant class type Multiple objects allowed Flag distribution class type Unique identification of the class type. Name of class type Database table for the master record that can also be linked to an object link. Indicatorthat impacts the sequence of screens for class maintenance. If this field is checked, the characteristics screen is displayed in the screen sequence when maintaining and displaying the class. Flag specifying whether the documents screen should appear in the screen sequence for a class type when maintaining and displaying the class. If this field is checked, the text screen is displayed when maintaining and displaying the class. If this field is checked, the standards data screen is displayed in the screen sequence when maintaining and displaying the class. If this field is checked, classifications in this class type can be amended, with reference to the effective date. You can then make changes to classifications that are only valid up to a particular effective date. The classification is maintained with a change number, which includes the date until which the change is valid. This flag enables classifications to be edited with change numbers, for which the validity is stipulated via parameters (e.g. serial numbers). Flag specifying that change documents are created in the class type for all changes in the classification. Flag specifying that objects from several classes may be assigned within a class type. Flag specifying that objects are only classified via master data maintenance and not via the classification system's central assignment function. Flag specifying that classes in the variant configuration can be used. This flag indicates whether different types of object may be classified in classes for this class type. This is useful to consolidate objects that interrelate logically into consolidated classes. Class type in which objects are classified, which need to be transported using ALE from one SAP system to another SAP system. Object Determination Softproviding Core User Documentation 8/39

9 Hierarchy allowed Table generation for object search Indicator specifying that a class hierarchy can be created for classes with this class type. This field controls in which tables the classification values for classification are saved Maintain Class Type Class status 1. Click on Class status in the menu tree. 2. Click the New Entries button. The following fields and flags will be available to you to enter data for each new Class status object. Fields and flags for the object Class status Class status Text Class maintenance allowed Classification allowed Selection allowed Default status flag for class maintenance Flag: Distribution lock Profile name ALE change authorization Flag specifying whether a class may be managed, whether objects may be assigned to a class and whether the class may be used when selecting objects. Text for a table entry If this field has been checked for a status, classes with this status can be changed via class maintenance. If this field has been checked for a status, objects can be assigned to classes with this status. If this field is checked, a search may be made for objects in a class with this status. This flag specifies which status should be proposed when creating a class. Flag that controls the distribution of object data in ALE systems for Integrated Distributed PDM Solution (ID PDM). Name of the profile that maps the distribution and control of change authorizations in ALE systems for ID PDM. Caution At least one "incomplete system" class status must be maintained. Without this status, it is not possible to save the customer-specific class type. Example Class type Class status 1 Z01 Object Determination Softproviding Core User Documentation 9/39

10 Text Class maintenance allowed Classification allowed Selection allowed Default status flag for class maintenance Flag: Distribution lock Profile name ALE change authorization Storage group free X X X We recommend that you create the following status for the class type for object determination: Storage group free Status = 1 Text = Storage group free Flag class maintenance, classification, selection allowed Storage group locked Status = 2 Text = Storage group locked Flag = class maintenance, selection allowed Incomplete manual Status = 3 Text = Incomplete manual Flag = none Automatic release Status = 4 Text = Automatic release Flag = none Incomplete system Status = 5 Text = Incomplete system Flag = class maintenance, classification, selection allowed Text types 1. Click on Text Types in the menu tree. 2. Click the New Entries button. The following fields and flags will be available to you to enter data for each new Text type object Fields and flags for the object Text type Type ID text block Unique identification of the class type. Flag to distinguish texts for different applications (e.g. purchase order texts, quotation texts). Object Determination Softproviding Core User Documentation 10/39

11 ID text type Text Area (Long) Text type Flag for the various uses of a text within a text area. Application in which this text is used. Specification of the various types of use within a text area. Example Type ID text block ID text type Text Area (Long) Text type Z01 Z1 Z1 Long text Classification status 1. Click on Classification Status in the menu tree. 2. Click the New Entries button. The following fields and flags will be available to you to enter data for each new classification status object. Fields and flags for the object classification status Class type Status of the classification Flag classification released Flag classification locked Classification incomplete manual Classification: incomplete by system Automatic release Unique identification of the class type. Specifies whether the assignment for the class search is released or locked. Flag for the status of the classification. All assignments with this status are released and found via the object search. Objects classified with the status 'locked' can be excluded from the object search. With this status, the user flags assignments that have not yet been fully evaluated. The status must be set if no value has yet been selected for characteristics for which an entry is required. Objects classified with the status 'incomplete' can be excluded from the object search. This status is assigned internally by the system if objects are assigned to a class without evaluating the characteristics. However, the system has recognized the class includes characteristics that need to be entered. The status incomplete is displayed for the classification on the interface. Flag that permits classifications to be released automatically. The flag may only be set in addition to another status flag. If it is set in connection with the status flag Incomplete system, a classification that was locked by the system can also be released by the system. Object Determination Softproviding Core User Documentation 11/39

12 At the same time, the system checks whether the classification was fully evaluated (i.e. all mandatory characteristics) and whether it is consistent. Caution As a minimum, the classification status needs to be created with the Incomplete system flag activated, to enable the newly defined class type to be saved. Example Class type Status of the classification 1 Flag classification released Flag classification locked Classification incomplete manual Classification: incomplete by system Result Z01 X With the settings applied, the customer-specific object Class type can now be used for object determination. Object Determination Softproviding Core User Documentation 12/39

13 2.2 Softproviding Core Classes Overview The class determines which class type including characteristics is used in object determination. Prerequisites An Object table has been assigned to the class type. The class type attributes: Class status, text types, classification status have been fully maintained. Procedure IMG menu Softproviding Core > Baseline > Determination > Object Determination > Classes 1. Call up the stated customizing table to maintain the class. 2. Click the New Entries button. The following fields and flags will be available to you to enter data for each new Class object. Enter values in all fields. Fields and flags for the object Class Plant Class type Class number Preallocate objects Example Plant 001 Class type Class number Preallocate objects Key that uniquely identifies a plant. Unique identification of the class type. Name that uniquely identifies a class in a class type. If this flag is checked, the objects are identified from customizing when creating an object plan. Z01 HÄLFTENKÜHLRAUM X Object Determination Softproviding Core User Documentation 13/39

14 3. Click the Save button to save your entries. Result With the settings applied, objects can now be assigned to a class Objects Overview If objects need to be automatically created when creating the object plan, this needs to have been previously specified in Customizing. Prerequisites A class has already been created. Procedure IMG menu Softproviding Core > Baseline > Determination > Object Determination > Classes 1. Call up the stated customizing table to maintain the classes. 2. Select the class for which objects need to be created. 3. Click on Objects in the menu tree. 4. Click the New Entries button. The following fields and flags will be available to you to enter data for each new Object object. Enter values in all fields. Fields and flags for the object Object Object Object description In this section, you specify objects with a text and a priority for each plant. Objects can be e.g. pigs, halves, cows, calves. They can be freely defined. Each object has a class and specific characteristics (inputs). Object description Sorting (object determination) Object determination: sorting of objects in object plans. 5. Click the Save button to save your entries. Object Determination Softproviding Core User Documentation 14/39

15 Example Object LAGRP1 Object description Storage group 1 Sorting (object determination) 10 Object texts are language-dependent. Result With the settings made, it is now possible to display predefined objects in a certain order when creating an object plan Output Fields Overview The result of object determination is the determination of an object based on characteristic values. In addition to the object, output fields can be used to ascertain further information for an object. Prerequisites A class has already been created. Procedure IMG menu Softproviding Core > Baseline > Determination > Object Determination > Classes 1. Call up the stated customizing table to maintain the classes. 2. Select the class for which objects need to be created. 3. Click on Output Fields in the menu tree. 4. Click the New Entries button. The following fields and flags will be available to you to enter data for each new Output field object. Enter values in all fields. Object Determination Softproviding Core User Documentation 15/39

16 Fields and flags for the object Output field Objects: Output field Field identifier short Field identifier medium Field identifier long Column name Example In this section, you specify the output fields for each plant and an output text. The output fields are the result of an object determination (output). Output fields can be e.g. destinations or specific tracks in an external warehouse management system. Names can be assigned as a leading text to a Dynpro field with reference to the ABAP dictionary. The text is then displayed on the Dynpro in the user's login language (if the text has been translated into this language). Names can be assigned as a leading text to a Dynpro field with reference to the ABAP dictionary. The text is then displayed on the Dynpro in the user's login language (if the text has been translated into this language). Names can be assigned as a leading text to a Dynpro field with reference to the ABAP dictionary. The text is then displayed on the Dynpro in the user's login language (if the text has been translated into this language). ALV control: column heading Objects: Output field 1 Field identifier short Mat. No. Field identifier medium Material No. Field identifier long Material Column name Mat. No. Object texts are language-dependent. Result With the settings applied, it is now possible to establish further information in addition to the object as the result of object determination. Object Determination Softproviding Core User Documentation 16/39

17 2.2.4 Interface Fields Overview The class characteristics represent the search criteria used to identify objects in an object plan. As well as the SAP GUI transaction /SPDGS/OBJF, the activating process can be an ABAP program or external system. In order to be able to transfer the search parameters from the process making the call to object determination, interface fields need to be defined and assigned to the class characteristics. Prerequisites The class has been fully created in Customizing. The master data for object determination (class and characteristics) have been maintained for the class characteristics to be assigned. Caution If the master data has not been maintained, no assignment to interface fields is possible! The class characteristics are not available for selection! Procedure IMG menu Softproviding Core > Baseline > Determination > Object Determination > Interface Fields 1. Call up the stated customizing table to maintain the interface fields. 2. Click the New Entries button. The following fields and flags will be available to you to enter data for each new interface field object. Enter values in all fields. Fields and flags for the object Interface field Plant Characteristic Key that uniquely identifies a plant. Field for the interface structure /SPDGS/S_LAGRP_FIND Unique name identifying a characteristic. Caution Customizing interface fields is not relevant for transport. The Interface fields and Object characteristics assignment must be reflected in each system. No transport takes place from the development system into the quality and production system! Object Determination Softproviding Core User Documentation 17/39

18 The standard interface fields are consolidated in the ABAP structure /SPDGS/S_LAGRP_FIND. The append technology can be used to include other customer-specific fields in the interface structure. Example Plant 0001 Characteristic Result SLGEW SLGEW_SW With the settings made, it is now possible to transfer the search parameters from the calling process, e.g. the ABAP program or external system to object determination. Object Determination Softproviding Core User Documentation 18/39

19 3 Application Object Determination Softproviding Core User Documentation 19/39

20 3.1 Master Data Class Administration Overview Object determination is based on the SAP classification system. Objects are consolidated into classes and described using class characteristics. Prerequisites SAP standard customizing of the classification system has been completed. Procedure SAP menu Transaction Cross-Application Components > Classification System > Master Data> Class Administration Softproviding Core > Baseline > Determination > Object Determination > Class Administration CL02 1. Start the Class Administration activity using one of the specified options. The Class Administration start screen is displayed. 2. Create a new class for your object determination. To see the extensive range of options for creating classes, please refer to the relevant SAP standard documentation: classification system (CA-CL). 3. Click the Save button to save your entries. Example Class Class type HÄLFTENKÜHLRAUM Z01 (storage group class) Result With the settings applied, class characteristics can now be created. Object Determination Softproviding Core User Documentation 20/39

21 3.1.2 Characteristics Administration Overview Object determination is based on the SAP classification system. Objects are consolidated into classes and described using class characteristics. Prerequisites A class has been created. Procedure SAP menu Transaction Cross-Application Components > Classification System > Master Data> Characteristics Administration Softproviding Core > Baseline > Object Determination > Characteristics Administration CL04 1. Start the Class Administration activity using one of the specified options. The Class Administration start screen is displayed. 2. Create a new characteristic for your object determination. To see the extensive range of options for creating characteristics, please refer to the relevant SAP standard documentation: classification system (CA-CL). 3. Click the Save button to save your entries. Example Class Class type Characteristic Name Characteristic Name HÄLFTENKÜHLRAUM Z01 (storage group class) LMC Proportion of flesh SLGEW_SW Slaughtering weight Result With the settings applied, class characteristics can now be created. Object Determination Softproviding Core User Documentation 21/39

22 3.2 Plan Management Object plans are managed centrally in the Plan Management menu. There are two options for managing object determination plans: General overview Individual plan editing for the effective date. Both options provide functions for creating, changing, copying and deleting an object plan General Overview Overview If you use the General Overview administration menu, you will obtain a list of all object plans for the selected class in the first step Display Object Plan Prerequisites An object plan has been created for the class. Procedure SAP menu Transaction Softproviding Core > Baseline > Object Determination > Plan Management /SPDGS/OBJF 1. Start the Plan Management activity using one of the specified options. The Plan Management start screen is displayed. The following fields are available for selecting object plans. Enter values in all fields. Fields and flags for selecting object plans Plant Class type Class Key that uniquely identifies a plant. Unique identification of the class type. Name that uniquely identifies a class in a class type. The transaction /SPDGS/OBJF replaces the obsolete transactions /SPDGS/LPLA, /SPDGS/LPLB and /SPDGS/LPLC. Object Determination Softproviding Core User Documentation 22/39

23 2. Click the Display button in the General Overview administration menu to display the object plans for the class in display mode. Example Plant 0001 Class type Z01 Class HÄLFTENKÜHLRAUM Result You can now select object plans for a class and display their details Change Object Plan Prerequisites A class has been created. Procedure SAP menu Transaction Softproviding Core > Baseline > Object Determination > Plan Management /SPDGS/OBJF 1. Start the Plan Management activity using one of the specified options. The Plan Management start screen is displayed. The following fields are available for selecting object plans. Enter values in all fields. Fields and flags for selecting object plans Plant Class type Class Key that uniquely identifies a plant. Unique identification of the class type. Name that uniquely identifies a class in a class type. The transaction /SPDGS/OBJF replaces the obsolete transactions /SPDGS/LPLA, /SPDGS/LPLB and /SPDGS/LPLC. 2. Click the Change button in the General Overview administration menu to display the object plans for the class in change mode. Object Determination Softproviding Core User Documentation 23/39

24 Caution All object plans for the class are locked in change mode! Example Plant 0001 Class type Z01 Class HÄLFTENKÜHLRAUM In change mode, the following functions for managing object plans are available: Create plan Copy plan Change plan validity Change plan Delete plan Function: Create plan 1. Click the Create Plan button to create a new object plan with a template. 2. Enter a validity period in the pop-up window. The following fields are available. Enter values in all fields. Fields and flags for object validity From To Date valid from Date valid to 3. Enter a name for the object plan in the Object plan description field. 4. Click the Save button to save your entries. An object plan, including the objects defined in Customizing, is created. Function: Copy plan 1. Select an object plan in the ALV list that you wish to copy. 2. Click the Copy plan button to create a copy of the selected object plan. 3. Enter a validity period in the pop-up window. The following fields are available. Enter values in all fields. Fields and flags for object validity From Date valid from Object Determination Softproviding Core User Documentation 24/39

25 To Date valid to 4. Confirm the validity limits by clicking Continue. 5. Enter a description for the object plan in the Object plan description field or leave the existing description as copied. 6. Click the Save button to save your entries. A copy of the selected object, including objects, is created. The validity periods of the existing object plans are amended so that only one object plan is ever valid for each date. Function: Change plan validity 1. Select an object plan in the ALV list whose validity you wish to change. 2. Click the Change plan validity button. 3. Enter a validity period in the pop-up window. The following fields are available. Enter values in all fields. Fields and flags for object validity From To Date valid from Date valid to 1. Confirm the new validity limits by clicking Continue. After confirming the new validity limits by clicking on the Continue button, the validities for the other object plans in the class are updated. All objects plans for a class have to be updated so that only one object is ever valid for each date. Example Before amending the plan validity for plan 2: Plan name: Valid from: Valid to: Plan Plan Plan validity for plan 2 changes from to After amending the plan validity for plan 2: Plan name: Valid from: Valid to: Plan Plan Click the Save button to save your entries. Object Determination Softproviding Core User Documentation 25/39

26 Function: Change plan 1. Select an object plan from the ALV list that you wish to change. 2. Click the Change plan button. This automatically takes you to the "Individual plan editing for effective date" administration menu. Please read section for a more detailed description of the options for amending an object plan. 3. Click Back to go back to the change menu in the general overview. 4. Click the Save button to save your plan changes. Function: Delete plan 1. Select an object plan from the ALV list that you wish to delete. 2. Click the Delete plan button. 3. Click Save to irreversibly confirm deletion of the object plan. Result You can now select object plans for a class and edit the selected object plans or add new object plans Individual Plan Editing for the Effective Date Display Object Plan Prerequisites An object plan has been created for the class. Procedure SAP menu Transaction Softproviding Core > Baseline > Object Determination > Plan Management /SPDGS/OBJF 1. Start the Plan Management activity using one of the specified options. The Plan Management start screen is displayed. The following fields are available for selecting an object plan. Enter values in all fields. Object Determination Softproviding Core User Documentation 26/39

27 Fields and flags for selecting object plans Plant Key that uniquely identifies a plant. Class type Unique identification of the class type. Class Name that uniquely identifies a class in a class type. Effective date Date on which the object plan is valid The transaction /SPDGS/OBJF replaces the obsolete transactions /SPDGS/LPLA, /SPDGS/LPLB and /SPDGS/LPLC. 2. Click the Display button in the Individual plan editing for the effective date administration menu to display the object plans for the class for the effective date. Example Plant 0001 Class type Z01 Class HÄLFTENKÜHLRAUM Effective date Result You can now select an object plans for a class and display details of the selected object plan Change Object Plan Prerequisites An object plan has been created. Procedure SAP menu Transaction Softproviding Core > Baseline > Object Determination > Plan Management /SPDGS/OBJF 1. Start the Plan Management activity using one of the specified options. The Plan Management start screen is displayed. The following fields are available for selecting object plans. Enter values in all fields. Object Determination Softproviding Core User Documentation 27/39

28 Fields and flags for selecting object plans Plant Key that uniquely identifies a plant. Class type Unique identification of the class type. Class Name that uniquely identifies a class in a class type. Effective date Date on which the object plan is valid Example Plant 0001 Class type Z01 Class HÄLFTENKÜHLRAUM Effective date The transaction /SPDGS/OBJF replaces the obsolete transactions /SPDGS/LPLA, /SPDGS/LPLB and /SPDGS/LPLC. 2. Click the Change button in the Individual plan editing for the effective date administration menu to display the object plans for the class in change mode. Caution All object plans for the class are locked in change mode! The following information is displayed in the object plan for each object Status Object Planned Actual Characteristic value(s) Individual objects can be set to status active or inactive. Object determination does not consider objects with the status of inactive. Objects can be freely defined. Each object has a class and specific characteristics (inputs). Object description Planned quantity for the object. The planned quantity can be specified for each object. A check is made with each object determination run to see whether the planned quantity is equal to the actual quantity. If the planned and actual quantities for an object are equal, a status of inactive is assigned to the object and is thus not considered. If no planned quantity has been entered, the object remains available without restriction. Actual quantity for the object. The actual quantity increases by one with each object determination run. Characteristic value(s) for the object. The first value for the characteristic is displayed. If other values exist, these can be displayed and changed using the Multiple characteristics function. Object Determination Softproviding Core User Documentation 28/39

29 Output field(s) Output value(s) for the object. Example Status Object Planne d Actua l Slaughtering weight Proportion of flesh Mat. No. Active LAGRP1 Store grp ,000 kg 1 % 4711 Inactive LAGRP2 Store grp ,000 5,000 kg 2 % 4712 Active LAGRP3 Store grp ,000 kg 4713 In change mode, the following functions for managing an object plan are available: Change activation status Change order Add rows Delete rows Copy object Reset actual Perform test determination Save Function: Change activation status 1. Select the icon in the Status column of the object to be activated or deactivated. A red circle in the Status column means that the object is inactive. A green square in the Status column means that the object is active. 2. Click the Save button to confirm the status change. Function: Change order 1. Select the Row selection button for the object that needs to be repositioned in the ALV list. The objects in an object plan are searched from top to bottom, according to the order in the ALV list. 2. Drag the selected object to the new position in the ALV list. 3. Click the Save button to confirm the position change. Function: Add rows 1. Click the Add rows button. A row is added at the end of the object plan. Object Determination Softproviding Core User Documentation 29/39

30 The following fields are available for maintaining a new object Status Object Planned Characteristic value(s) Output field(s) Individual objects can be set to status active or inactive. Object determination does not consider objects with the status of inactive. Objects can be freely defined. Each object has a class and specific characteristics (inputs). Object description Planned quantity for the object. The planned quantity can be specified for each object. A check is made with each object determination run to see whether the planned quantity is equal to the actual quantity. If the planned and actual quantities for an object are equal, a status of inactive is assigned to the object and is thus not considered. Characteristic value(s) for the object. The first value for the characteristic is displayed. If other values exist, these can be displayed and changed using the Multiple characteristics function. Output value(s) for the object. on the Object field An object can be added either independently of customizing or via the customizing-dependent F4 Help. If an object is added independently of customizing, the object description is not language-dependent. If an object is added from customizing, the object description is language-dependent. 2. Click Save to confirm addition of the new object. Function: Delete rows 1. Select one or more objects in the ALV list. 2. Click the Delete rows button. 3. Click Save to confirm deletion of the objects from the object plan. Function: Copy object 1. Select the object in the ALV list that should be used as a template for the copy. 2. Click the Copy object button. 3. In the pop-up window, enter an object name in the Object field and an object description in the field for the new object When copying, the characteristic values are also copied from the copy template. 1. Click the Continue button to confirm the entries. 2. Select the icon in the Status column of the new object to activate it. 3. Click Save to confirm creation of the new object. Object Determination Softproviding Core User Documentation 30/39

31 Function: Reset actual 1. Select one or more objects in the ALV list. 2. Click the Reset actual button. The value in the Actual column is reset to Click Save to confirm the resetting of the actual value for the objects from the object plan. Function: Perform test determination 1. Click the Perform test determination button. 2. Enter the values for the characteristics provided. The Insert Rows button in the pop-up window has no function. As this pop-up window is a SAP standard dialog box, it cannot be hidden. After a test determination run, the value in the ACTUAL field is not increased. 3. Click the Continue button to confirm the entries. Function: Save 1. Click the Save button to confirm amendments to the object plan. Object Determination Softproviding Core User Documentation 31/39

32 3.3 Program Interfaces Object Determination Calls Instead of using the SAP GUI transaction /SPDGS/OBJF, it is possible to call up object determination from programs by using Softproviding Core, an ABAP function module or classification methods. ABAP Function Module /SPDGS/OF_API_FINDING RFC function module for object determination. This function module will determine the object for the characteristics for the class to be transferred (in structure /SPDGS/S_LAGRP_FIND). If the characteristic does not exist in structure /SPDGS/S_LAGRP_FIND, this field must be added as an append in the structure. The number which is passed on in parameter I_MIST is increased in the actual quantity of the determined object. /SPDGS/OF_API_PLAN_COPY Object Determination: Copy plan. /SPDGS/OF_API_PLAN_OBJ_C HANGE This function module allows you to copy an object plan. Parameter IX_RESET is used to reset all planned quantities to zero. Parameter IX_COMMIT is used to execute COMMIT WORK (X) or COMMIT WORK AND WAIT (W) in the function module Object Determination: Change object in plan. This function module allows you to change the following information on the object plan: Activation statusstatus Sorting Planned quantity of the object Object description These fields are only adjusted if the indicator for changes is set. Also, the contents of the output fields can be amended. ABAP OO Class /SPDGS/CL_OF_PLAN Static method OBJECT_FINDING_WITH_KEY_DATE Instance method OBJECT_FINDING Object Determination Softproviding Core User Documentation 32/39

33 3.3.2 BAdIs The following Business Add-Ins are available for customer-specific enhancements to object determination: /SPDGS/BADI_OF_CLASS Method CHECK_AUTHORITY: The AUTHORITY_CHECK function module can be implemented in a static method to check the SAP user executing the object determination against an authorization object. /SPDGS/BADI_OF_PLAN Method SAVE: The instance method is executed after the object plan has been saved. If the Save function is called up from the General Overview administration menu, the method for each object plan for the class is called up. If the Save function is called up from the Individual Plan Editing administration menu, only the method for the object plan for the class opened in change mode is called up. Object Determination Softproviding Core User Documentation 33/39

34 3.4 Authorizations In the previous release 2.40, the authorization object /SPDGS/OF was created for Object Determination. For further information on the issue of authorizations, please see the Softproviding Core Security Guide. By implementing the BADI /SPDGS/BADI_OF_CLASS, there is an option to implement a customerspecific authorization check in the AUTHORITY_CHECK method. Object Determination Softproviding Core User Documentation 34/39

35 4 Technology Comparison: Object Determination vs. Determination Application Object Determination Softproviding Core User Documentation 35/39

36 4.1 Assignment of the Corresponding Determination Application Elements Object determination - element Object plan Determination application - element Determination application Determination application - description A determination application can have one or more levels (sequences). The levels are consolidated in a determination schedule. A determination application usually has input fields at each level that are searched and output fields that constitute the results of the determination. Object Level A level saves data depending on a unique search key. Characteristics Search fields Search fields are the input fields for a field group, which are searched for the purposes of the determination. Output fields Output fields Output fields of a field group that constitute the results of the determination. Object Determination Softproviding Core User Documentation 36/39

37 4.2 Comparison of Elements Object determination - element Pros Cons Object plan Amendment of search order in the production system with no transport order SAP standard and Softproviding customizing objects required => extensive customizing Object plan of the relevant authorization concept Definition of the validity period only cross-object New authorization object /SPDGS/OF for Object Determination Integration in DPS workbench only possible by creating DPS wrapper function module Determination application - element Determination application Pros Cons Only Softproviding customizing objects required => lean customizing Definition of search order only possible in the customizing system Integration in DPS workbench possible without creation of DPS wrapper function module No authorization concept Object determination - element Pros Object De/activation in production system possible Re-creation in production system possible Determination application - element Pros Level Parallel editing of levels by different users possible Definition of validity period for each level Cons Lock all object plans in the class for object amendment Cons De/activation possible in Customizing system only No creation in production system possible Object determination - element Pros Characteristics Maintenance of several values for each characteristic possible Value restriction inclusive and exclusive possible Cons SAP standard customizing object required => extensive customizing Object Determination Softproviding Core User Documentation 37/39

38 Object determination - element Determination application - element Pros Maintenance of value ranges possible Pros Search fields No SAP standard customizing object required => lean customizing Cons Cons No maintenance of several values for each characteristic possible Only inclusive value restriction possible No maintenance of value ranges possible Object Determination Softproviding Core User Documentation 38/39

39 4.3 Conclusion Object plan area of operation If the following criteria for managing business process data apply, the use of object determination technology is recommended: Complex search criteria Authorization concept required Automatic deactivation of business process data Ad hoc changes directly in the production system required Solid SAP proficiency in business departments Application determination area of application If the following criteria for managing business process data apply, the use of application determination technology is recommended: Simple search criteria No authorization concept required SAP department should have overall responsibility for administration Little SAP proficiency in business departments Object Determination Softproviding Core User Documentation 39/39