Documentation for Program SAPKKA12

Introduction

Program SAPKKA12 sets the CO status for sales orders involved in results analysis to DLV (delivered), FNBL (final billing), TECO (technically completed), and CLSD (closed).

Up to Release 4.0B, the statuses FNBL and DLV were employed to realize period-based representation of the states final billing and delivered for results analysis. This is no longer necessary from Release 4.5A onwards, or if Note 104678 is installed. The two statuses are determined on the basis of the period when the order is processed in results analysis.

If a results analysis method is used that creates reserves for unrealized costs after the status final billing or delivered is set, these reserves should be canceled when the status technically completed is set.

Once the status closed has been set, no further postings on the sales order item are possible. The sales order item is then no longer involved in results analysis. This is an attribute that can be used to reduce the runtime of results analysis (see Note 83562). Since program SAPKKA12 (like results analysis itself) reads a large amount of data from the database, you should decide whether SAPKKA12 should be run monthly or less frequently.

All four statuses set by this program can also be set or cleared manually in the maintenance of the sales order item.

Program SAPKKA12 has been enhanced in several stages. The present document applies to Release 4.6C. The newest version is available in Note 116363. The present document also applies to this note, with minor exceptions. With older versions, more differences can be expected.

Initial Screen

Group restricts the sales order items to be selected. Only items that have a variance key can be selected.

Selection of sales orders:

Order type ____ to ____Sales order __________ to __________Item ______ to ______Results analysis key ______ to ______

Organization data:Company code ____ to ____

Plant ____ to ____

SD organization data Sales organization ____ to ____ Distribution channel __ to __ Division __ to __ Sales office ____ to ____ Sales group ___ to ___

In the test run mode (group ), the changes determined are shown in the results list but are not written to the database.

Processing options:

Test run

In group you can specify whether all selected items are shown in the results list, or only those for which a status was changed. You can also specify whether the transferred dependent items are displayed. The transferred dependent items are described in the explanation for group .

Display:

All selected itemsAll changed items With transferred dependent items

In block you can specify whether the status final billing should not be changed, or whether this status should be set or cleared in accordance with the evaluation of the SD documents.

Document flow in SD:

Do not change “Final billing” or

Set status “Final billing” If the item has status “Final billing”, otherwise clear.

In group you can specify whether the status delivered should not be changed, or whether this status should be set or cleared in accordance with the evaluation of the SD documents.

Document flow in SD:

Do not change “Delivered” or

Set status “Delivered” If the item has been delivered, otherwise clear.

In block you specify the period (year/period) for which the two statuses final billing and delivered should be checked. You cannot enter this period directly. Instead, the system derives the period and the year from the current date less the number of periods in the past. You must enter only the number of periods in the past. Include SD document flow for changing “Final billing” and “Delivered” until

Period ___Year ____calculated from the current period less the number of the lastprevious periods _?

The settings in group establish the criteria for changing the status technically completed. The following settings must be made: (mandatory) The period/year since no costs and revenues may have been incurred. The

credit from the settlement of the item is not taken into account here (optional) At least one cost or revenue posting must exist. This is usually appropriate. (optional) The item and all dependent items (see group ) must have the status final billing. (optional) The item and all dependent items (see group ) must have the status delivered. (optional) All dependent orders must have the status delivered or technically

completed. The dependent orders are all production orders and internal orders that areassigned to the item or to one of the dependent items (). With theproduction orders, only the orders for the nonvaluated sales order or project stock count.

(mandatory) The SD/CO standard check must be passed. This check itself has different optional settings that are explained in group .

All selected criteria must be fulfilled (AND operation) to enable the status to be set.

At the beginning of group you can specify whether the status technically completed is not changed, whether it is set if the criteria are met, or cleared if the criteria are not met (end of group ).

Checking the dependent orders for the status delivered or technically completed can be appropriate because setting the status of an item to technically completed can have irreversible effects on the dependent orders.

Costs and revenues in CO and document flow in SD:

Do not change “Technically completed” or

Set status “Technically completed”

if no cost or revenue posting has taken place since (other than settlement of RA data)Period ___Year ____

calculated from the current period less the number of the lastprevious periods _?

and if the item has at least one posting has the status “Final billing” has the status “Delivered”

and if all dependent orders “Technically completed” or “Delivered”

and if the SD/CO standard check is passed

and clearif the conditions are not met.

The settings in group establish the criteria for changing the status closed. The following settings must be made: (mandatory) The period/year since no costs and revenues may have been incurred, and no credit

from settlement of the item, nor changes in results analysis data (optional) The item and all dependent items (see group ) and all dependent production orders

and other orders for the items are fully settled(balance = 0). It is not necessary for all individual objects to be settled. It is only necessary that thetotal sum of all objects is zero.

(optional) Final results analysis must have been performed on the item. This means that all reserves and inventories are zero

(optional) At least one cost or revenue posting must exist. This is usually appropriateto prevent the status from being set prematurely.

(optional) The item and all dependent items (see group ) must have the status final billing. (optional) The item and all dependent items (see group ) must have the status delivered. (optional) The item already has the status technically completed. That is, the status must already be

set. If one of the statuses technically completed or closed is to be set from thereleased, this condition may not be specified.

(optional) All dependent orders must have the status delivered or technicallycompleted. The dependent orders are all production orders and internal orders that areassigned to the item or to one of the dependent items ().

(mandatory) The SD/CO standard check must be passed. This check itself has different optional settings that are explained in group .

All selected criteria must be fulfilled (AND operation) to enable the status to be set.

At the beginning of group you can specify whether the status closed is not changed, whether it is set if the criteria are met, or cleared if the criteria are not met (end of group ).

Normally, it is recommended that you not check whether the status closed should be cleared if the criteria for setting the status are not met. The reason is that if this is not checked, the items with the status closed are not included in the checks, which improves the runtime.

Costs, revenues, RA data, status in CO, document flow in SD, SD/CO standard check:

Do not change “Closed” or

Set status “Closed”

If no cost or revenue posting or RA data sincePeriod ___Year ____

calculated from the current period less the number of the lastprevious periods _?

and if the item Completely settled Final results analysis

and if the item has at least one posting has the status “Final billing” has the status “Delivered” is Technically Completed

and if all dependent orders “Technically completed” or “Delivered”

and if the SD/CO standard check is passed

and clearif the conditions are not met.

The SD/CO standard check of group is the same check that is executed when you manually set the status in the maintenance of the sales order. This check procedure checks the following:

a) The conditions of general status maintenanceb) SD-specific conditions

For the business transaction Close:i) The full quantity to be invoiced of the sales item must be invoicedii) The overall processing status must be completed or not relevantiii) The object (the item) must be archivable (archiving check)iv) If according to standard (group ) was selected: A) Make-to-order production: All production orders for the item must be reorganizable B) Static assembly: It must be possible to set the deletion flag for the associated

assembly order. This is somewhat more rigorous than A), which merely checks the archiving for the order

If static assembly is involved, and if according to standard was selected in group , then after business transaction Close is performed the deletion flag for the assembly order is set and this change is marked for the update (if applicable). If without production orders was selected in group , no deletion flag is set for the assembly order, nor is the order marked for update.

The archiving check also checks whether the object has been completely settled (has a balance of zero). However, whether this check is performed depends on whether the settlement profile of the object specifies that the object must be settled. If the settlement profile specifies that the object can be settled or is not to be settled, the system does not check whether the balance is zero.

The conditions of general status management affect how both statuses (technically completed and closed) are set. All other conditions currently implemented affect only how the status closed is set.

A number of technical details for the SD/CO standard check are presented below. The status changes for the statuses closed and technically completed and the associated SD/CO standard check are described in function module SD_ITEM_CHANGE_STATUS. The conditions for general status management are stored in table TJ07. With the SD specific conditions, the routine STATUS_CHECK_XXXX(SAPLV45P) is called for transaction XXXX (if a routine of that name exists). Two such routines currently exist. One of these, STATUS_CHECK_BABS, is used here for business transaction Close (BABS). The archiving check is executed by function module K_OBJECT_REORG_CHECK. If T459K-MNTGA = 2 then static assembly is involved. When business transaction XXXX has been run, routine STATUS_FOLLOWUP_XXXX(SAPLV45P) is executed if such a routine exists. Currently, there is only a routine for business transaction Close (BABS). If static assembly is involved, the deletion flag is set for the assembly order and marked for the update. That is, CO_61_ORDER_POST is called up.

SD/CO standard check for status change Technically Completed and Closed: according to standard

without production orders

In Customizing for results analysis in the valuation methods, the field sales order structure can contain the value A, B, or K. This means that in results analysis for a sales order item, the costs and revenues of subordinate items can be included in summation and valuated together with the other items. Results analysis only updates data on the item on which results analysis was performed. Program SAPKKA12 determines whether the status should be changed for the item of results analysis. If you select Dependent items in group , these status changes are transferred to the dependent items. In this case, the dependent items should not have their own results analysis key.

Transfer status change “Technically completed” and “Closed” to

dependent items

Annotations: To determine the status “Final billing” and “Delivered” for an item, the subordinate items are included. To determine cost and revenue postings, all subordinate objects are included.

Output ListThe output list shows the processed items. There is a column for each of the four statuses. Legend:

Status not set, no change X Status set, no change ->X Status was setX-> Status was cleared* Not indicated, no change