martes, mayo 08, 2012

Funciones para trabajar en PS con numero interno (object number)

La mayoría de las tablas requeridas para desarrollos en PS , requieren la utilización de OBJNR (object number) la nota siguiente señala las funciones de conversión a utilizar (como usuario lo más sencillo es utilizar la transacción RKACSHOW).

Note 522246 - PS consulting: Internal and external number for project/WBS


Within a client, a unique 1:1 ratio exists between the external WBS element number and its respective internal number.

The internal number is part of the key on the database table. The external number is unique, this means the external number can similarly only occur (as the internal number also) in each client one single time.

The internal number is determined from the respective number range object when a project or WBS element are created. The object number of the object is created based on this internal number.
The conversion between internal and external number is processed with the following modules:
  • CONVERSION_EXIT_KONPD_INPUT
           converts the external project number into the internal project number (definition)
  • CONVERSION_EXIT_KONPD_OUTPUT
           converts the internal project number into the external project number (definition)
  • CONVERSION_EXIT_KONPR_INPUT
           converts the external WBS element number into the internal WBS element number
  • CONVERSION_EXIT_KONPR_OUTPUT
           converts the internal WBS element number into the external WBS element number
  • CONVERSION_EXIT_WILDC_INPUT
           converts the external WBS element number into the internal WBS element number (wildcards)
  • CONVERSION_EXIT_WILDC_OUTPUT
           converts the internal WBS element number into the external WBS element number (wildcards)
  • CONVERSION_EXIT_KONPS_INPUT
           standard WBS: converts the external project number into the internal project number
  • CONVERSION_EXIT_KONPS_OUTPUT
           standard WBS: converts the internal project number into the external project number
  • CONVERSION_EXIT_KONPT_INPUT
           standard WBS: converts the external WBS element number into the internal WBS element number
  • CONVERSION_EXIT_KONPT_OUTPUT
           standard WBS: converts the internal WBS element number into the external WBS element number

These conversions are carried out partly automatically, however, they can also be called 'manually'.

If they are called 'manually', the initiator is responsible for the consistency of the data. Conversion modules cannot return any exceptions and must therefore work with messages.

If, for example, CONVERSION_EXIT_KONPR_INPUT is called with an external number that is not compatible with the project coding mask (see project coding mask) (for example, letters in a numeric section), the program terminates.

Example for automatic conversion:
           You position the internal number of a WBS element on a screen by using DDIC field PRPS-PSPNR. Its data element PS_POSNR uses domain PS_POSNR which has KONPR defined as the conversion routine.
           
           This causes the internal WBS element number used in the program as the external number to be automatically displayed when this screen is processed (by CONVERSION_EXIT_KONPR_OUTPUT). This is actually the usual situation, in other words, if a WBS element is displayed on a screen, this is normally the automatically converted internal number.
           
           If you enter an external WBS number in the WBS element field, the system converts it automatically into the internal number (by CONVERSION_EXIT_KONPR_INPUT).
           
           As a result, it is not possible, for example, to search in Transaction SE16 in database tables for internal numbers. If an internal number is entered in field PSPNR, it is treated as an external number. Therefore the conversion fails, the project/WBS element is not found. Use Transaction SE17 here which does not carry out any conversion.

The internal number or the object number of the WBS element are stored in all reference objects in which the WBS element is used as the account assignment (network activity, purchase requisition, settlement rule, classification, CO document, FI document and so on).

This way the external number of the project or WBS element can subsequently be changed at any time; the internal number (and thus the consistency of the data) as a result remains unaffected.

A project or WBS element that is identified in different clients or in a distributed system by an identical external number have with almost certain probability different internal numbers.

For this reason, projects and WBS elements must not be copied from another system or client into a target system that is not empty because the internal number would thus also be copied.

In distributed systems, also the internal number is generally different for each system for a project or WBS element, however here identification takes place between the systems explicitly with the external number.

For this reason the external number is not changeable for ALE distribution.