SAP R/3 Implementation

Functional Specification of Extension

Status: Version:

Functional Specification

SAP system implementation

Keeping configuration of sales order item

in non-standard table

Document Information
Functional Specification – Extension Heading
Path of document
Application
Business Unit / Area
Team
Business/Process Owner
Person responsible for preparing
Functional Specification
Person responsible for extending
Functional Specification
Status:
Priority:
Complexity:
Y:\03_Zespol MM\06_Projekty techniczne i
funkcjonalne\03_Rozszerzenia
SD
Sales
OTC
Krzysztof Lis
Jarosław Karwowski
Not started / Started / Under review / Completed / Approved
High / Medium / Low
Simple / Medium / Complex / Very Complex

Related Documents
Document Comments

Modified: 2021-12-09 Page 1 of 9 Recently modified by:

09/12/2021 Jarosław Karwowski
 SAP R/3 Implementation
Functional Specification of Extension
Contents: Status: Version:

1 DOCUMENT INFORMATION............................................................................................................... 1

2 RELATED DOCUMENTS.................................................................................................................... 1

3 DOCUMENT HISTORY........................................................................................................................ 3
3.1 REVISION HISTORY.......................................................................................................................... 3
3.2 APPROVAL / SIGN - OFF................................................................................................................... 3
4 SCOPE AND KEY ASSUMPTIONS..................................................................................................... 3
4.1 FUNCTIONAL DESCRIPTION.............................................................................................................. 3
4.2 BUSINESS BENEFITS........................................................................................................................ 3
4.3 SCOPE............................................................................................................................................ 3
4.4 RELATIONSHIPS / LIMITATIONS......................................................................................................... 3
4.5 ASSUMPTIONS................................................................................................................................. 3
5 DETAILED SPECIFICATION OF FUNCTIONAL REQUIREMENTS...................................................3
5.1 FUNCTIONAL SPECIFICATION............................................................................................................ 3
5.1.1 Table of characteristics values...............................................................................................................3
5.1.2 Programme updating the table of characteristics..................................................................................5
5.2 REPORTING..................................................................................................................................... 5
5.3 PRELIMINARY CONFIGURATION OF CONVERSION DATA/REQUIREMENT...............................................5
6 TESTING CONDITIONS...................................................................................................................... 5
6.1 KEY BUSINESS TESTING CONDITIONS................................................................................................ 6
6.2 TECHNICAL TESTING CONDITIONS..................................................................................................... 6
6.3 ISSUES / RELATIONSHIPS CONNECTED WITH TESTING.......................................................................6
7 OPEN ISSUES..................................................................................................................................... 6

8 ATTACHMENT..................................................................................................................................... 6
8.1 DICTIONARY.................................................................................................................................... 6
8.2 ADDITIONAL SUPPORT / REFERENCE DOCUMENTATION.......................................................................6
8.2.1 Function returning characteristics values..............................................................................................6
8.2.2 Modification of format of characteristics values data.............................................................................9

Modified: 2021-12-09 Page 2 of 9 Recently modified by:

09/12/2021 Jarosław Karwowski
 SAP R/3 Implementation
Functional Specification of Extension
Status: Version:

Document History

Revision History
Author Version Rev. date Summary of changes Section Page

Jarosław Karwowski 1.0 29-09-2005 1-8

Approval / Sign - off

The hereby document requires the approval of the following persons:
(Signed approval forms are filed in the quality section of the project files)
Name Role Date Signature

Scope and key assumptions

Functional Description
Standard way of keeping configuration characteristics values is complicated and it may cause output
problems fin case of big number of processed data. The described functionality’s purpose is to keep
characteristics values in non-standard table parallel to standard solution.

Business benefits
This solution will allow ensuring optimal time of system response for new transactions (reports) based on
the configuration of sales orders items.

Scope
The extension concerns the sales process of steel industry products and semi-finished products, special
sale, administration of claims and rebates (all sales orders items contain products that can be configured).

Relationships / Limitations
No.

Assumptions
Values of all characteristics in a sales order item will be kept in non-standard table.

Detailed Specification of Functional Requirements

Functional Specification

1.1.1 Table of characteristics values

Table keeping characteristics values should consist of the following fields:

Field1 MANDT

Modified: 2021-12-09 Page 3 of 9 Recently modified by:

09/12/2021 Jarosław Karwowski
 SAP R/3 Implementation
Functional Specification of Extension
Field name (PL) Mandant Status: Version:
Field name (EN) Client
Key YES
Field type CLNT
Field length 3

Field2 ID
Field name (PL) ID
Field name (EN) ID
Key YES
Field type NUMC
Field length 18

Field3 VBELN
Field name (PL) Dokument Sprzedaży
Field name (EN) Sales Document
Key NO
Field type CHAR
Field length 10

Field4 POSNR
Field name (PL) Pozycja dokumentu sprzedaży
Field name (EN) Sales Document Item
Key NO
Field type NUMC
Field length 6

Field5 CUOBJ
Field name (PL) Konfiguracja
Field name (EN) Configuration
Key NO
Field type NUMC
Field length 18

Field6 KLART
Field name (PL) Rodzaj Klasy
Field name (EN) Class type
Key NO
Field type CHAR
Field length 3

Modified: 2021-12-09 Page 4 of 9 Recently modified by:

09/12/2021 Jarosław Karwowski
 SAP R/3 Implementation
Functional Specification of Extension
Status: Version:
Field 7 CLASS
Field name (PL) Klasa
Field name (EN) Class
Key NO
Field type CHAR
Field length 18

Field8 ATNAM
Field name (PL) Nazwa cechy
Field name (EN) Characteristic name
Key NO
Field type CHAR
Field length 30

Field 9 ATWRT
Field name (PL) Wartość cechy
Field name (EN) Characteristic value
Key NO
Field type CHAR
Field length 30

Estimated size of the table is ca. 10 000 entries daily.

1.1.2 Programme updating the table of characteristics

Each time a sales order is entered into memory, an output in the form of special function will be initiated.
This function will call the programme updating the table of characteristics. This solution ensures on-line
data transfer to the table after each modification in configuration of a sales order item.

The programme should copy characteristics values to the table for each sales order item which has
configuration (field VBAP-CUOBJ is filled). In case of modifications in a sales order and re-calling
updating programme, the programme should write new characteristics values over already existing lines
in the table.

In case of multiple-valued characteristics, the records in the table are entered in different ID field and they
have different characteristic value.

The example of a function returning characteristics values for a given configuration object (CUOBJ) is in
the attachment.

Reporting
No.

Preliminary Configuration of Conversion Data/Requirement

No.

Testing Conditions

Modified: 2021-12-09 Page 5 of 9 Recently modified by:

09/12/2021 Jarosław Karwowski
 SAP R/3 Implementation
Functional Specification of Extension
Status: Version:
Key business testing conditions
ID Condition Expected result Ref. Cycle
1 Verifying types and lengths of used Fields in table contain relevant data
fields in table with expected data to be formats.
kept
2 Checking if all characteristics values in All characteristics values of given sales
full configuration of a given sales order order item have been copied to the
item have been copied to the table table.
(repeating test for all class types,
including applying multiple-valued
characteristics)

1.2 Technical testing conditions

ID Condition Expected result Ref. Cycle

1 Entering new configuration of sales
order item
2 Configuration modification (change of
value in a given line in the table)
3 Errors service test
Recording data in the table
Modified record of data in the table
In case there are any errors in
updating entries in the table, sales
order may be entered

Issues / Relationships Connected with Testing

Full configuration of products classes at the mandant for testing is required to perform tests correctly.

Open Issues
No. of Description Assigned to Status Impact Solution
issue

Attachment

Dictionary
Notion Definition

Additional support / reference documentation

1.2.1 Function returning characteristics values

The above function returns all characteristics values of a given configuration object in class type 300. This
function can also return characteristics values of configuration of a batch in class type 023 for a given
combination of material no. – batch no. The function should be adjusted to service multiple-valued
characteristics (control).

Modified: 2021-12-09 Page 6 of 9 Recently modified by:

09/12/2021 Jarosław Karwowski
 SAP R/3 Implementation
Functional Specification of Extension
FUNCTION Z_GET_KOMPAZ.Status: Version:
*"---------------------------------------------------------------
-------
*"*"Local interface:
*" IMPORTING
*" VALUE(CUOBJ) LIKE KOMP-CUOBJ
*" VALUE(MATNR) LIKE KOMP-MATNR OPTIONAL
*" VALUE(CHARG) LIKE KOMP-CHARG OPTIONAL
*" EXPORTING
*" REFERENCE(ZZSTEEL_GRADE) TYPE KOMP-ZZSTEEL_GRADE
*"------------------------------------------------------------
* This function takes a CUOBJ, gets the characteristic of
*referenced material and return them. If CUOBJ is initial
*obteins it with Matnr and Charg.

CONSTANTS: C_MARA LIKE INOB-OBTAB VALUE 'MARA',

C_MCH1 LIKE INOB-OBTAB VALUE 'MCH1',
C_300 LIKE INOB-KLART VALUE '300',
C_023 LIKE INOB-KLART VALUE '023'.
DATA: L_D_ATNAM LIKE CABN-ATNAM,
L_D_ATFOR LIKE CABN-ATFOR,
L_D_ANZDZ LIKE CABN-ANZDZ,
L_D_CUOBJ LIKE INOB-OBJEK,
L_D_OBTAB LIKE INOB-OBTAB,
L_D_KLART LIKE INOB-KLART,
L_D_INOB_CUOBJ LIKE INOB-CUOBJ.
* characteristic values for the instance
TYPES: IBCO2_VALUE_REC LIKE IBVALUE0.
TYPES: IBCO2_VALUE_TAB TYPE IBCO2_VALUE_REC OCCURS 0.
*Table with the structure of Valuation of characteristics
DATA: I_VALUES TYPE IBCO2_VALUE_TAB.
DATA : L_D_VALUE TYPE IBCO2_VALUE_REC.
IF CUOBJ IS INITIAL.
CLEAR: L_D_CUOBJ, L_D_INOB_CUOBJ, L_D_OBTAB, L_D_KLART.
L_D_CUOBJ(18) = MATNR.
L_D_CUOBJ+18(10) = CHARG.
IF CHARG IS INITIAL.
L_D_OBTAB = C_MARA.
L_D_KLART = C_300.
ELSE.
L_D_OBTAB = C_MCH1.
L_D_KLART = C_023.
ENDIF.
SELECT CUOBJ INTO L_D_INOB_CUOBJ FROM INOB
WHERE KLART = L_D_KLART
AND OBTAB = L_D_OBTAB
AND OBJEK = L_D_CUOBJ.

Modified: 2021-12-09 Page 7 of 9 Recently modified by:

09/12/2021 Jarosław Karwowski
 SAP R/3 Implementation
Functional Specification of Extension
ENDSELECT. Status: Version:
SELECT * FROM AUSP
INTO CORRESPONDING FIELDS OF TABLE I_VALUES
WHERE OBJEK = L_D_INOB_CUOBJ.

ELSE.

REFRESH: I_VALUES.
CALL FUNCTION 'CUCB_GET_VALUES_FROM_INSTANCE'
EXPORTING
IV_INSTANCE = CUOBJ
IMPORTING
ET_VALUES = I_VALUES
EXCEPTIONS
INVALID_INSTANCE = 1
OTHERS = 2.
ENDIF.

* For every characteristic take its name and format

LOOP AT I_VALUES INTO L_D_VALUE.
* Load values into output parameters
CLEAR : L_D_ATNAM, L_D_ATFOR, L_D_ANZDZ.
SELECT SINGLE ATNAM ATFOR ANZDZ FROM CABN
INTO (L_D_ATNAM, L_D_ATFOR, L_D_ANZDZ)
WHERE ATINN = L_D_VALUE-ATINN.
CASE L_D_ATNAM.

WHEN 'STEEL_GRADE'.
PERFORM F_GET_VAL USING L_D_VALUE
L_D_ATFOR
L_D_ANZDZ
ZZSTEEL_GRADE.

ENDCASE.
ENDLOOP.

ENDFUNCTION.

Modified: 2021-12-09 Page 8 of 9 Recently modified by:

09/12/2021 Jarosław Karwowski
 SAP R/3 Implementation
Functional Specification of Extension
Status: Version:

1.2.2 Modification of format of characteristics values data

*&---------------------------------------------------------------
------*
*& Include *
*&---------------------------------------------------------------
------*
*& Form F_GET_VAL
*------------*
* -->PE_VALUE Register VALUES
* -->PE_ATFOR Characteristic Format
* -->PE_ANZDZ Decimals number
* <--PS_NUM_VALOR Characteristic value
*----------------------------------------------------------
*------------*

FORM F_GET_VAL USING PE_VALUE TYPE IBVALUE0

PE_ATFOR
PE_ANZDZ
PS_VALOR.

CASE PE_ATFOR.
WHEN 'NUM' or 'CURR'.
PE_VALUE-ATFLV = PE_VALUE-ATFLV * ( 10 ** PE_ANZDZ ).
PS_VALOR = PE_VALUE-ATFLV.
WHEN 'CHAR'.
PS_VALOR = PE_VALUE-ATWRT.
ENDCASE.

ENDFORM. " F_GET_VAL*

Date of translation : October 14, 2005

Modified: 2021-12-09 Page 9 of 9 Recently modified by:

09/12/2021 Jarosław Karwowski