Technical Specification

Technical Specification
Module MM

Document # Outbound Program

Program Name ZINTR_S2S_NOKIA_PO

Program Type Create / Change Create
Program type Conversion Batch Interface Online
Interface Report
(select the check box)
Form Enhancement Extension
Dialog

Modification Unknown Others

BAPI

ALE/ IDOC Application Development

Revision History
Version Date Description of changes

00 23.12.2013 Interface program for Nokia PO S2S Project

Technical Specification Page 1 of 11 Date 8/1/2024

 Technical Specification

Technical Design

Process Logic :

Proxy Name - PO_DATA_REQ has been created.

Header Data –
Object Name in Enterprise Services Builder | Name of an Object in R/3

1. contactName ----- CONTACT_NAME

2. EmailAddress_fromRole ----- EMAIL_ADDRESS_FROM_ROLE
3. telephoneNumber_fromRole ----- TELEPHONE_NUMBER_FROM_ROLE
4. globalPartnerRoleClassificationCode_fromRole ----- GLOBAL_PARTNER_ROLE_CLASSIFICA
5. globalBussinessIdentifier_fromRole ------ GLOBAL_BUSSINESS_IDENTIFIER_FR
6. globalSupplyChainCode_fromRole ------ GLOBAL_SUPPLY_CHAIN_CODE_FROM
7. globalPartnerClassificationCode_fromRole ------ GLOBAL_PARTNER_CLASSIFICATION1
8. comments ----- COMMENTS
9. globalDocumentFunctionCode ------- GLOBAL_DOCUMENT_FUNCTION_CODE
10. dateTimeStamp ------- DATE_TIME_STAMP
11. globalDocumentReferenceTypeCode ------
GLOBAL_DOCUMENT_REFERENCE_TYPE
12. proprietaryDocumentIdentifier -------- PROPRIETARY_DOCUMENT_IDENTIFIE
13. globalPurchaseOrderTypeCode --------
GLOBAL_PURCHASE_ORDER_TYPE_COD
14. dropShip ------- DROP_SHIP
15. GlobalSpecialHandlingCode ------- GLOBAL_SPECIAL_HANDLING_CODE
16. GlobalBusinessIdentifier_shipTo ------ GLOBAL_BUSINESS_IDENTIFIER_SHI
17. GlobalLocationIdentifier ------ GLOBAL_LOCATION_IDENTIFIER
18. addressLine1 ------- ADDRESS_LINE1
19. addressLine2 ----- ADDRESS_LINE2
20. addressLine3 ------ ADDRESS_LINE3
21. cityName ------ CITY_NAME
22. GlobalCountryCode ----- GLOBAL_COUNTRY_CODE
23. nationalPostalCode ------ NATIONAL_POSTAL_CODE

Technical Specification Page 2 of 11 Date 8/1/2024

 Technical Specification

24. documentGenerationDateTime ------ DOCUMENT_GENERATION_DATE_TIME

25. documentIdentifier ------ DOCUMENT_IDENTIFIER
26. contactName_toRole ----- CONTACT_NAME_TO_ROLE
27. EmailAddress_toRole ------ EMAIL_ADDRESS_TO_ROLE
28. GlobalPartnerRoleClassificationCode_toRole ----- GLOBAL_PARTNER_ROLE_CLASSIFIC1
29. GlobalBusinessIdentifier_toRole ------ GLOBAL_BUSINESS_IDENTIFIER_TO
30. globalSupplyChainCode_toRole ------- GLOBAL_SUPPLY_CHAIN_CODE_TO_RO
31. globalPartnerClassificationCode_toRole ------- GLOBAL_PARTNER_CLASSIFICATION

Item Data –
Object Name in Enterprise Services Builder | Name of an Object in R/3

1. globalProductUnitOfMeasureCode ---- GLOBAL_PRODUCT_UNIT_OF_MEASURE

2. dropShip ---- DROP_SHIP
3. lineNumber ---- LINE_NUMBER
4. orderQuantity ----- ORDER_QUANTITY
5. proprietaryInformation --- PROPRIETARY_INFORMATION
6. dateStamp ----- DATE_STAMP
7. globalTransportEventCode ----- GLOBAL_TRANSPORT_EVENT_CODE
8. GlobalPartnerClassificationCode ----- GLOBAL_PARTNER_CLASSIFICATION
9. GlobalPartnerClassificationCode_M ----- GLOBAL_PARTNER_CLASSIFICATION1
10. proprietaryProductIdentifier ----- PROPRIETARY_PRODUCT_IDENTIFIER
11. proprietaryProductIdentifier_M ----- PROPRIETARY_PRODUCT_IDENTIFIE1

ZNOKIA_FRESH_PO_S2S is attached to output type – ZNK1.

This program called ZINTR_S2S_NOKIA_PO.

Fetched data from EKKO on the basis of screen PO.

On the basis of EKKO-EKGRP fetched data from T024.
On the basis of PO Number (EKKO-EBELN) fetched data from EKPO .

Technical Specification Page 3 of 11 Date 8/1/2024

 Technical Specification

Fetched data (ADRNR) from T001W on the basis of EKPO-WERKS.

Fetched EINDT from EKET on the basis of EKPO-EBELN and EKPO-EBELP.
On the basis of T001W-ADRNR fetched address detail from ADRC.

Pass all above details to Proxy Sturcture.

HEADER

contact_name = it_ekko-eknam.
email_address_from_role = 'Test'.
telephone_number_from_role = '1234567890'.
global_partner_role_classifica = 'Buyer'.
global_bussiness_identifier_fr = '650089493' .
global_supply_chain_code_from = 'Electronic Components'.
global_partner_classification1 = 'Shopper'.
global_document_function_code = 'Request'.
comments = it_ekko-lifnr.
date_time_stamp = Concatenate EKKO-AEDAT and 'T000000.000Z'
global_document_reference_type = 'Purchase Order'.
proprietary_document_identifie = ekko-ebeln .
global_purchase_order_type_cod = 'Standard'.
drop_ship = 'No'.

global_special_handling_code = 'Test'.
global_business_identifier_shi = '650089493'.
document_generation_date_time = Concatenate ekko-bedat 'T134419.000Z'
document_identifier = ekko-ebeln.
contact_name_to_role = it_ekko-eknam.
email_address_to_role = 'Test' .
global_partner_role_classific1 = 'Seller'.
global_business_identifier_to = '368400438'.
global_supply_chain_code_to_ro = 'Electronic Components'.
global_partner_classification = 'Manufacturer'.
address_line1 = adrc-name1.
address_line2 = T001w-name2.
address_line3 = T001w-stras.
city_name = adrc-city1.
national_postal_code = adrc-post_code1.
global_country_code = 'IN'.
global_location_identifier = ekpo-matkl.
global_special_handling_code = ekpo-werks.

Technical Specification Page 4 of 11 Date 8/1/2024

 Technical Specification

DETAIL

global_product_unit_of_measure = 'Piece'.
drop_ship = 'No'.
line_number = ekpo-ebelp.
order_quantity = ekpo-menge.
proprietary_information = 'Nokia Product code'.
date_stamp = Concatenate ekpo-eindt and 'Z'.
global_transport_event_code = 'Ship'.
proprietary_product_identifier = ekpo-matnr.
global_partner_classification = 'Shopper'.
proprietary_product_identifie1 = ekpo-matnr.
global_partner_classification1 = 'Manufacturer'.

If EKKO-BSART = 'ZNKP' and EKKO-EKORG = 'NKPO' it will send the data to NOKIA.
CALL METHOD cl_ref->po_data_req
EXPORTING
output = it_output
IMPORTING
input = it_input.
Return value will be maintained in Z-TABLE - znokia_status.

Technical Specification Page 5 of 11 Date 8/1/2024

 Technical Specification

21) Code Review Checklist

Technical Specification Page 6 of 11 Date 8/1/2024

 Technical Specification

Sl. Description Self Reviewer Comments Fixed Date

No. Review

General

1 Is the name of program as Y

mentioned in the specification/
naming standards of SAP/ITC

2 Is coding sequence of events in

appropriate order? Y

3 Events described in development Y

approach are used?

4 Are text elements being maintained Y

in required languages and hard
coded information removed

5 Is formatting of amount and Y

quantity fields done by using
CURRENCY and UNIT options

6 Is clearing of work areas done, Y

wherever required?

7 Is function key assignment as per Y

the standards ?

8 Have all the keys been mentioned Y

in SELECT SINGLE.?

9 SELECT * has NOT been used Y

10 Aggregate clauses are NOT used in Y

SELECT. (viz. SUM, COUNT, ORDER
BY, GROUP BY)

11 CHECK statement is not used in Y

SELECT - ENDSELECT loop

12 Has the clause 'FOR ALL ENTRIES' Y

been used instead of a nested
select

Technical Specification Page 7 of 11 Date 8/1/2024

 Technical Specification

13 Has the internal table used in the Y

"FOR ALL ENTRIES IN " been
checked for emptiness ?

14 Are all SELECTs coded outside Y

LOOP - ENDLOOP?

15 Is the Binary search clause used N

with the read table statement ?

16 Has the clause "INTO TABLE Y

<Internal table>" been used instead
of INTO CORRESPONDING FIELDS
OF INTERNAL TABLE ?

17 Has the entire table key been Y

specified in the select clause of the
statement which contains the
addition "for all entries in " ?

18 Has the clause "APPENDING Y

TABLE Internal table" been used
instead of APPENDING
CORRESPONDING FIELDS OF
internal table

19 Have the internal tables been Y

sorted by appropriate keys before
being looped at or being used in a
read statement ?

20 Appropriate message classes and Y

types used

21 In a where clause have the fields Y

been put in the same order as the
existing index ?

22 In a where clause have the tests N

which restrict the data most been
put in the first position ?

23 Are all the possible screen Y

validations done.

Technical Specification Page 8 of 11 Date 8/1/2024

 Technical Specification

24 Has the delete where clause been Y

used instead of delete statement
inside a loop endloop ?

25 Has "delete from internal table" Y

been used instead of deleting the
records inside a loop ?

26 Has the transporting clause been Y

used along with the 'MODIFY
internal table ' statement ?

27 In case of mass updation has the NA

modify table from itab been used
instead of using modify statement
inside a loop ?

28 Have implanted loops been used Y

instead of implanted selects ?

29 There is no duplicate SELECT Y

statements

30 If the development includes BDC, NA

have the user default settings been
taken into account while posting
numeric values ?

31 In programs where file(s) are read Y

from or written to, does the
program check for the emptiness of
the file and hence terminate
without proceeding further ?

32 In case of SMARTFORM have all N

SELECT statements are coded in
the INITIALIZATION block

33 Has all the exceptions are handled N

during a CALL FUNCTION ?

34 Are names self explanatory and NA

prefixed by sequence numbers

Technical Specification Page 9 of 11 Date 8/1/2024

 Technical Specification

35 Are Forms and Modules ordered Y

36 Are Function modules and related Y

logic included in separate Forms,
wherever necessary

37 Is SY-SUBRC checked after each N

call to a function module.

38 Usage of correct parameters (field Y

lengths and data types) while using
CALL FUNCTION

Code Alignment, Spacing and Formatting

39 Are ‘=’, ‘TO’, ‘TYPE’ and ‘VALUE’ in Y

variable declarations aligned

40 Are Internal Comments aligned Y

41 Are logically different Coding Y

Blocks separated by blank lines

42 Is the format for SQL statements Y

correct

43 Are ‘ENDIF’, ‘ENDLOOP’, ‘ENDAT’ Y

etc. commented (if necessary) to
indicate the IF, LOOP etc. they
belong to

Error Handling

44 Are ‘divide by zero’ errors checked, Y

by checking value of the divisor to
be nonzero before each division

45 Are size errors being checked, by Y

ensuring that the sizes of variables
used for storing totals and
additions are large enough to hold
anticipated maximum values

46 Is SY-SUBRC checked after CALL, Y

Technical Specification Page 10 of 11 Date 8/1/2024

 Technical Specification

OPEN, READ, and SQL statements

Extended Check and Clean Up

47 Is extended program check Y

completed and all errors/warnings
removed

48 Code inspector (SCI) Status Y

49 Runtime Analysis (SE30) Status Y

50 SQL Trace (ST05) Status Y

Sign off – Technical Specification

Prepared By Shweta Singh
23.12.2013
Date

Approved By Sandeep Verma

Date

Technical Specification Page 11 of 11 Date 8/1/2024