Enhancing Output Determination

1 Enhancing Output DeterminationTechnical Solution GuideThe Smith Consulting Group, Box 703 Flanders, NJ and R/3are the trademarks or registered trademarks of SAP AGin Germany and in several other 2004 The Smith Consulting Group, Inc. All Rights Output Determination6/19/2005 Page2of47 Technical Solution GuideCopyright 2004 The Smith Consulting Group, Inc. All Rights Output Usage Areas Relevant for Output Structures by Application Field Catalog the Field Condition Function OSS 1 Filling the Header 2 Call Function 3 Call Function 4 Filling the Item 5 Call 6 Call Function 7 Call Function Order Confirmation Output Enhancement 1 Create a new field for use in Output 2 Make ZZ_RTI_ORDER available to the field 3 Populating the ZZ_RTI_ORDER 4 Adding ZZ_RTI_ORDER to the field 5 Building the new condition 6 Adding the new condition table to the access 7 Creating aSales Rep customer 8 Maintaining the condition Output Enhancement 1 Create a new field for use in Output 2 Populating the AUART 3 Build the Requirement 4 Assigning the routine to an

2 Output 5 Testing the 6 Running the VOFM Output Determination6/19/2005 Page3of47 Technical Solution GuideCopyright 2004 The Smith Consulting Group, Inc. All Rights Output DeterminationOutput Determination is one of several functions that use the R/3 condition technique. Thepurpose of this document is to demonstrate how to enhance Output Determination using thestandard user exits built into R/3. In many cases, designing a successful enhancementrequires both functional configuration and program logic. This document explains the userexit functionality, and then details two sample enhancements taken from actual projects. Theexamples were built on a document assumes that the reader understands the condition technique and it s configuration for Output Usage CodeThe condition technique is used in several areas of SD (Pricing, OutputDetermination, etc.)

3 All of these areas share the same functions and programs for maintaining condition records,etc. To differentiate between these areas, the Condition Usage Code is used. The conditiontechnique for Output Determination is identified via usage code B . Many of the objects related to Output Determination contain this code in either the object name or as a high orderkey in configuration tables. For example, building condition table 900 in outputdetermination creates a physical table name B900. In pricing, where the condition usage codeis A , the physical table name is A900. Enhancing Output Determination6/19/2005 Page4of47 Technical Solution GuideCopyright 2004 The Smith Consulting Group, Inc. All Rights AreaThe Application Area subdivides the condition usage of the condition technique (forexample, sales order, billing, purchase order).

4 The communication structures and processingfunctions for Output Determination are built separately for each application area. TableT681A contains all application areas defined in R/3. Table T681Z contains the subset ofthose application areas that are relevant for Output Determination . The following list is Areas Relevant for Output DeterminationAreaDescriptionCFError controlCVDocument administrationDBCustomersE1 Inbound deliveryEAPurchasing RFQEFP urchase OrderELPurchasing Scheduling Agreement ReleaseESData entry sheetEVPurchasing Outline AgreementK1 Sales activitiesM1 Rough Goods ReceiptMDDirect buyingMEInventory managementMRInvoice verificationNFNota fiscalP1 Direct ManufacturingPAJIT callRSAutomotiveV1 SalesV2 ShippingV3 BillingV4 Shipping (Special case) Enhancing Output Determination6/19/2005 Page5of47 Technical Solution GuideCopyright 2004 The Smith Consulting Group, Inc.

5 All Rights unitsV7 TransportW0 All. table GroupW1 Sales promotion groupWAAllocation tableWBRetail promotionWELabelingWNFree Sett. Rel. Sett. AgreementWTTrading contractEnhancing Output Determination6/19/2005 Page6of47 Technical Solution GuideCopyright 2004 The Smith Consulting Group, Inc. All Rights StructuresR/3 uses work areas called communication structures to pass data from the callingapplication to the Output Determination functions. There are separate structures for headerand item data (when relevant). In many cases, the communication structures contain specialincludes for customer specific enhancements. Only these special includes should be modifiedby the customer. The following example is the delivery header communication structure. Thefirst screen displays the top portion of the Output Determination6/19/2005 Page7of47 Technical Solution GuideCopyright 2004 The Smith Consulting Group, Inc.

6 All Rights the bottom of the structure, theincludefor customer enhancements is found(KOMKBZ4). These includes always contain the field DUMMY. This field exists because inearlierversions of R/3, the data dictionary did not allow structures that contained no put the DUMMY field into these structures just to get around this requirement. Whencustomer specific fields are added to these structures, the DUMMY field shouldbe several occasions, we have seen programmers actually leave the DUMMY field as is, butuse it as an indicator for some purpose. We strongly recommend that this practice not beused. If a field is required, it should be created with a relevantname and data Output Determination6/19/2005 Page8of47 Technical Solution GuideCopyright 2004 The Smith Consulting Group, Inc.

7 All Rights Structures by Application AreaTable T681Z contains the communication structure names for each application area. Thename usually corresponds to the application area, but there are exceptions. Notice in thefollowing list that application areas EA and EF use the same header StructureItem StructureCFKOMKBCFCVKOMKBCVDBE1 KOMKBE1 EAKOMKBEAEFKOMKBEAKOMPBEAELKOMKBEAESKOMK BESEVKOMKBEAK1 KOMKBK1M1 KOMKBM1 MDKOMKBMDMEKOMKBMEKOMPBMEMRKOMKBMRKOMPBM RNFKOMKBNFP1 KOMKBP1 PAKOMKBPARSKOMKBRSV1 KOMKBV1 KOMPBV1V2 KOMKBV2 KOMPBV2V3 KOMKBV3 KOMPBV3V4V5 KOMKBV5V6 KOMKBV6V7 KOMKBV7W0 Enhancing Output Determination6/19/2005 Page9of47 Technical Solution GuideCopyright 2004 The Smith Consulting Group, Inc. All Rights StructureItem StructureW1 WAKOMKBWAKOMPBWAWBKOMKBWBKOMPBWBWEKOMKBW EWNKOMKBWNWRKOMKBWRKOMPBWRWSKOMKBWSWTKOM KBWTKOMPBWTE nhancing Output Determination6/19/2005 Page10of47 Technical Solution GuideCopyright 2004 The Smith Consulting Group, Inc.

8 All Rights Field CatalogThe field catalog is a configuration table (T681F) that contains all fields that can be used askey fields when building condition tables. When the fieldcatalog is maintained, the availablefield list is based on the fields contained in the field catalog Catalog StructureThere are separate field catalogs for each condition usage code. For Output Determination , thefield catalog structureis KOMB. Like the communication structures, the field catalogstructure contains anincludefor customer specific fields (KOMBZ). Enhancing Output Determination6/19/2005 Page11of47 Technical Solution GuideCopyright 2004 The Smith Consulting Group, Inc. All Rights this example, the KOMBZ include has been modified with several new fields. TheDUMMY field was Output Determination6/19/2005 Page12of47 Technical Solution GuideCopyright 2004 The Smith Consulting Group, Inc.

9 All Rights the Field CatalogThe field catalog maintenance transaction is found next to the corresponding condition tablemaintenance transaction in the IMG. Although the field catalog transaction is listed second, itis processed Output Determination6/19/2005 Page13of47 Technical Solution GuideCopyright 2004 The Smith Consulting Group, Inc. All Rights field catalog maintenance program is a standard SM30 screen that maintains tableT681F. All field catalogs used in the condition technique are contained in T681F. The highorder keys of this table are the condition usage code and application area. Since thistransaction maintains the field catalog for sales orders, the T681F entries maintained are fromcondition usage code B and application area V1 . While adding fields, the valid field list consists of the fields in the field catalog structure (KOMB).

10 Enhancing Output Determination6/19/2005 Page14of47 Technical Solution GuideCopyright 2004 The Smith Consulting Group, Inc. All Rights Condition TablesWhen building condition tables, the available fields in the right pane, are the fields fromT681F in the corresponding condition usage and application area. ( B , V1 ). Enhancing Output Determination6/19/2005 Page15of47 Technical Solution GuideCopyright 2004 The Smith Consulting Group, Inc. All Rights Function ModulesThere are two main function groups used foroutput Determination . V61B contains the mainfunctions that enable Output Determination . VCOM contains functions and user exits forfilling the communication structures with document data from the calling OSS NotesThe following OSS notes may be helpful in understanding Output name added to new condition table39462 Expand field catalog in message determination159684 Not all fields are displayed in condition tableProcess FlowThe following diagram and screen shots illustrate how the processing functions are calledusing sales order Output as an Output Determination6/19/2005 Page16of47 Technical Solution GuideCopyright 2004 The Smith Consulting Group, Inc.