Vous êtes sur la page 1sur 19

Technical Specification

For
HEX Enhancements
Technical Specification for Pestana

General Organization / Project Name


Pestana
Information
Associated Documentation

Business Name Role Signature Date


Owner

Created By Name Dept. Function / Role Signature Date


Rahul Technical

Recommended Name Dept. Function / Role Signature Date


Signees

Document Version Reason for Change Valid as of


History Date
1.1 New fields added 03/28/2019

Applicable Sections
1,3

Page 2of 19
Technical Specification for Pestana

Table of Contents
1 Summary ....................................................................................................................... 4
1.1 Business Requirements ......................................................................................................4
1.2 Business value ...................................................................................................................4
2 Functional Requirements ............................................................................................... 4
2.1 Detailed Specification ........................................................................................................4
2.2 Flow Chart .........................................................................................................................5
2.3 Field Mappings ..................................................................................................................5
2.4 Proto type of User Interface (UI).........................................................................................5
2.5 Performance Criteria ..........................................................................................................5
3 Technical Specification ................................................................................................... 6

4 Interface Requirements................................................................................................ 13
3.1 Volume of Data ................................................................................................................ 13
3.2 Performance Criteria ........................................................................................................ 13
5 Data Conversion Requirements .................................................................................... 14
4.1 Detailed Specification ...................................................................................................... 14
4.2 Transfer Protocol Details .................................................................................................. 14
4.3 Field Mappings ................................................................................................................ 14
4.4 Volume of Data ................................................................................................................ 14
4.5 Performance Criteria ........................................................................................................ 14
6 Reporting Requirements .............................................................................................. 15
5.1 Detailed Specification ...................................................................................................... 15
5.2 Reporting Layout ............................................................................................................. 15
5.3 Reporting Input Screens ................................................................................................... 15
5.4 Performance Criteria ........................................................................................................ 15
6 Assumptions, Security and Unit Testing ........................................................................ 16
6.1 Assumptions .................................................................................................................... 16
6.2 Security ........................................................................................................................... 16
6.3 Unit Test Plan (Internal – Not for Client Review) ............................................................... 16

Page 3of 19
Technical Specification for Pestana

1 Summary
1.1 Business Requirements
HEX extract for Customer Master and AR enhancement
1.2 Business value

The extract that we are getting from HEX for AR and Customer master needs additional
fields for collections cloud implementation.
2 Requirements
2.1 Detailed Specifications

Customer Master Extract Enhancement


Field Name Source
Last yr sale Customer Master
Last 2 yr sale Customer Master
Account clerk Customer Master
Credit limt Credit Master
DSO Credit Master
Credit insurance limit Customer Master
Vendor number Customer Master
Vendor clearing flag Customer Master

Order value Placeholder for client to key in values


Cash mgt group Placeholder for client to key in values
Property reference Customer Master

Page 4of 19
Technical Specification for Pestana

AR Extract Enhancement:

Field Name Source


AR
Local currency 2
AR
Local currency 2 amt
Placeholder for client to key in values
Class
Placeholder for client to key in values
% Provision
AR
GL account

As part of the AR extract, we also wish to include vendor invoices along with the above.

Contacts Extract Enhancement:


Work in progress- will be updated in v2

2.2 Flow Chart


NA
2.3 Field Mappings
NA
2.4 Proto type of User Interface (UI)
NA
2.5 Performance Criteria
NA

Page 5of 19
Technical Specification for Pestana

3 Technical Specification:
a) Customer Master Extract Enhancement:
Enhancement Spot: /HEX/ES_CUST_EXTRACT_FIELDS
BADI Definition: /HEX/BD_CUST_EXTRACT_FIELDS
Method: FETCH_ADDITIONAL_DATA

Implement the above BADI and write the below logic inside FETCH_ADDITIONAL_DATA
method.
1) Add the additional fields column name in the include
“CT_CUST_ADDITIONAL_FILEDS ” structure of ‘/HEX/S_CUST_ADDITIONAL_FILEDS’
of the changing parameter .
Component Component Type
LAST_YR_SALE TBD
LAST_2YR_SALE TBD
ACCOUNT_CLERK BUSAB
CREDIT_LIMIT KLIMK
DSO DSOIN_F02L
CREDIT_INSURANCE_LIMIT VLIBB
VENDOR_NUMBER LIFNR
VENDOR_CLEARING_FLAG XVERR
ORDER_VALUE TBD
CASH_MGT_GROUP FDGRV
PROPERTY_REFERENCE RECAOBJNR

2) Put Select query on table KNB1 and get KUNNR, BUKRS, BUSAB, XVERR, FDGRV and
VLIBB into a local table (say LT_BUSAB) for all entries present in IT_CUST_HEADER
where KUNNR is equal IT_CUST_HEADER-KUNNR and BUKRS is equal
IT_CUST_HEADER-BUKRS.

Page 6of 19
Technical Specification for Pestana

3) Put select query on table T001 and get BUKRS and KKBER into a local table (say
LT_T001) for all entries in IT_CUST_HEADER where BUKRS is equals to
IT_CUST_HEADER-BUKRS.
4) Put select query on table KNKK and get KUNNR, KKBER and KLIMK into a local table
(say LT_KNKK) for all entries in IT_CUST_HEADER where KUNNR =
IT_CUST_HEADER-KUNNR.
5) Put select query on table KNA1 and get KUNNR and LIFNR into a local table (say
LT_LIFNR) for all entries in IT_CUST_HEADER where KUNNR is equals to
IT_CUST_HEADER-KUNNR.
6) Put select query on BSID table and get the value of fields BUKRS KUNNR ZUONR
fields into LT_BSID internal table for all entries in IT_CUST_HEADER table where
BUKRS is equals to IT_CUST_HEADER-BUKRS and KUNNR is equals to
IT_CUST_HEADER-KUNNR.
a. Put select query on VIBDOBJASS table and get the value of OBJNRSRC
OBJNRTRG fields into table (LT_VIB) for all entries in LT_BSID where
OBJNRTRG is equal to LT_BSID-ZUNOR.
b. Put select query on table VICNCN and get the value of fields INTRENO OBJNR
into internal table (Say LT_VIC) for all entries in LT_VIB where OBJNR is
equals to LT_VIB- OBJNRSRC.
7) Now loop at table IT_CUST_HEADER into work area (say LS_CUST_HEADER), get the
KUNNR and BUKRS fields and do the following with each record: -
o Pass the value of LS_CUST_HEADER-KUNNR & LS_CUST_HEADER-BUKRS
to field CUST_NUMBER and COMP_CODE of changing parameter
“CT_CUST_ADDITIONAL_FILEDS” respectively.

o Put read statement on local internal table LT_BUSAB and get the value of
fields BUSAB, XVERR, FDGRV and VLIBB for keys KUNNR is equals to
LS_CUST_HEADER-KUNNR and BUKRS is equal to LS_CUST_HEADER-

Page 7of 19
Technical Specification for Pestana

BUKRS and pass the value of BUSAB, XVERR, FDGRV and VLIBB to field
ACCOUNT_CLERK, VENDOR_CLEARING_FLAG, CASH_MGT_GROUP and
CREDIT_INSURANCE_LIMIT of changing parameter
CT_CUST_ADDITIONAL_FILEDS respectively.

o Put read statement on local internal table LT_LIFNR and get the value of
field LIFNR for key KUNNR which is equal to LS_CUST_HEADER-KUNNR
and pass the value of LIFNR field to VENDOR_NUMBER of changing
parameter CT_CUST_ADDITIONAL_FILEDS.

o Put read statement on local internal table LT_T001 and get the value of
field KKBER for key BUKRS is equal to LS_CUST_HEADER-BUKRS.

o Put read statement on LT_KNKK internal table and get the value
of KLIMK for key KUNNR is equal to LS_CUST_HEADER-KUNNR and
KKBER is equals to LT_T001-kkber and populate it to field
CREDIT_LIMIT of changing parameter
CT_CUST_ADDITIONAL_FILEDS.

o Call the Function module ‘CUSTOMER_DSO_CALCULATION’ and pass the


value LS_KNKK-KKBER and LS_KNKK-KUNNR to exporting parameter
I_KKBER and I_KUNNR, get the value of DSO from E_DSOIN exporting
parameter and populate it to DSO field of the
CT_CUST_ADDITIONAL_FILEDS changing parameter.
o Put read statement on BSID table and get the value of field ZUONR for
key BUKRS is equals IT_CUST_HEADER-BUKRS and KUNNR is equals to
IT_CUST_HEADER-KUNNR.

Page 8of 19
Technical Specification for Pestana

o Loop LT_VIB table and get the value of OBJNRSRC field for key
OBJNRTRG is equals to LT_BSID-ZUNOR and concatenate the value
of OBJNRSRC into local variable (say: lv_obj) for each record
separated by pipe ‘|’.
 Pass the value of lv_obj to PROPERTY_REFERENCE field of
changing parameter CT_CUST_ADDITIONAL_FILEDS.

b) AR Extract Enhancement:
Prerequisites:
1) Go to Transaction /HEX/AR_CONFIG.
2) Click on ‘AR Configuration’ node as shown below:

3) Execute AR by clicking on execute button .

4) Click on Edit button and select the check box for all default BSID table fields.

Page 9of 19
Technical Specification for Pestana

5) To add header for additional column in AR extract file, select the checkbox
for field name “ZFIELD01”, “ZFIELD02”, “ZFIELD03”, “ZFIELD04”, “ZFIELD05”
& ZFIELD06 and provide column name as “Local Currency 2”, ”Local Currency
2 amount”, “Class”, “% Provision” & “GL account” respectively. Save the
changes.

Program Logic:
Required configuration:
Tcode: /HEX/EXT_CONFIG
Maintain the required accounting clerks for variable name as
‘ACCOUNTING_CLERK’ separated by comma.

(Above image is for reference purpose)

Page 10of 19
Technical Specification for Pestana

Enhancement Spot: /HEX/ES_EXTRACT


BADI Definition: /HEX/BD_AR_EXTRACT
Method: ENHANCE_AR_EXTRACT
 Implement the BADI and write logic inside method
“ENHANCE_AR_EXTRACT”.
 Put a select query on BSID table to get the values of fields “DMBE2”(Amount
in Second Local Currency) , “HKONT”( General Ledger Account) into lt_bsid
for all entries of table IT_EXTRACT where fields “BUKRS” , “GJAHR” ,
“BELNR” & “BUZEI” is equals IT_EXTRACT-BUKRS, IT_EXTRACT-GJAHR,
IT_EXTRACT-BELNR & IT_EXTRACT-BUZEI” respectively .
 Put a select query on T882 table to get the values of field bukrs curr2 into
LT_T882 for all entries of table IT_EXTRACT where bukrs is equals to
IT_EXTRACT-bukrs.
 Put a select query on ‘T1’ table to get the values of fields “class” and
“%Provision” for all entries of table IT_EXTRACT into internal table IT_T1.
 Create a custom table ZPT_CCODE having fields company code and country
as shown below.
Company Code Country

Above table will store only Portugal (i.e PT) company codes.
 Put a select query on table ZPT_CCODE and get the values of all fields into
the local table LT_COMPANYCODE_COUNTRY.
 Put select query on table /hex/ext_config and get value of ATTR_VALUE
where ATTR_NAME is equal to ‘ACCOUTING_CLERK’ into ls_config(local
workarea) .
o Put split statement on ls_config- ATTR_VALUE at comma( , ) and get
the value in local internal table(say LT_ACC_CLERK).

Page 11of 19
Technical Specification for Pestana

 Put a select query on KNB1 and get the value of KUNNR, BUKRS and BUSAB
into table LT_KNB1 for all entries in IT_EXTRACT where fields ‘KUNNR’ and
‘BUKRS’ is equals to IT_EXTRACT-KUNNR and IT_EXTRACT-BUKRS
respectively.
 Put a select query BSID to get the values of fields “ZUONR”(Assignment ID) ,
“XREF3”( Reference key 3) into LT_BSAD for all entries in table IT_EXTRACT
where fields “BUKRS” , “GJAHR” , “BELNR” & “BUZEI” is equals IT_EXTRACT-
BUKRS, IT_EXTRACT-GJAHR, IT_EXTRACT-BELNR & IT_EXTRACT-BUZEI”
respectively .
 Now loop at IT_EXTRACT for each record and get the value of field BUKRS,
GJAHR, BELNR, BUZEI and pass it to BUKRS, GJAHR, BELNR, BUZEI of
changing parameter “ET_ADD_EXTRACT_FIELDS” and do the following:
 For each record put read statements on local internal tables
IT_T1 and get the values of fields Class, % Provision and pass
the values to CONTENT field of changing parameter
ET_ADD_EXTRACT_FIELDS separated by horizontal tab.
 Put read statement on table lt_bsid and get the value of
DMBE2, HKONT for key bukrs is equals to IT_EXTRACT-BUKRS,
GJAHR is equals to IT_EXTRACT-GJAHR, BELNR is equals to
IT_EXTRACT-BELNR, BUZEI is equals to IT_EXTRACT-BUZEI and
populate it to CONTENT fields of ET_ADD_EXTRACT_FIELDS
changing parameter separated by horizontal tab.
 Put read statement on LT_T882 table and get the value of field
CURR2 for key BUKRS is equals to LT_EXTRACT-BUKRS and
populate it to CONTENT fields of ET_ADD_EXTRACT_FIELDS
changing parameter separated by horizontal tab.
(Note: Order of concatenating fields to CONTENT field and
column name should be same)

Page 12of 19
Technical Specification for Pestana

 Put a read statement on table LT_KNB1 into LS_KNB1 and get


the value of busab with key KUNNR is equal to IT_EXTRACT-
KUNNR and BUKRS is equal to IT_EXTRACT-BUKRS.
o Put a read statement on table LT_ACC_CLERK with key
BUSAB is equals to LS_KNB1-BUSAB.
o If SY-SUBRC is not equal to zero, put exist statement
then leave the field PO_NUMBER as blank of
ET_ADD_EXTRACT_FIELDS changing parameter
separated by horizontal tab.
o Else put a read statement on
LT_COMPANYCODE_COUNTRY for the key BUKRS is
equals to LT_EXTRACT-BUKRS.
 If SY-SUBRC is equal to zero, then put a read
statement on the table LT_BSID and get the
value of the field XREF3 (Reference key 3) for
the key BUKRS is equals to LT_EXTRACT-BUKRS,
KUNNR is equals to LT_EXTRACT-KUNNR and
populate it to the PO_NUMBER field of
ET_ADD_EXTRACT_FIELDS changing parameter
separated by horizontal tab..
 If SY-SUBRC not equal to 0, then put a read
statement on the table LT_BSID and get the
value of the field ZUONR (Assignment ID) for
the key BUKRS is equals to LT_EXTRACT-BUKRS,
KUNNR is equals to LT_EXTRACT-KUNNR and
populate it to the PO_NUMBER field of
ET_ADD_EXTRACT_FIELDS changing parameter
separated by horizontal tab.

Page 13of 19
Technical Specification for Pestana

c) Contacts Extract Enhancement:


Class: /HEX/CL_CUSTOMER_EXTRACT
Method: MAP_CONTACT_DET_TO_FILE
1) Open /HEX/CL_CUSTOMER_EXTRACT Class in SE24 and in the top menu select class
and click on Enhance.

2) Provide Enhancement implementation name


3) Now place a cursor on GET_CONTACT method and from top menu select EDIT ->
Enhancement Operations -> Insert Overwrite-Method.

Page 14of 19
Technical Specification for Pestana

4) Observe the post-exit created and click on that indication to navigate to enter the custom
code.

5) Copy paste the entire code from MAP_CONTACT_DET_TO_FILE method to overwrite-Exit.


6) Fetch the data as per requirement and populate it to required field of lw_cont structure.
(Note: Replace all global attributes and methods with core_object->.)
Below is one example

Page 15of 19
Technical Specification for Pestana

d) Vendor Extract:
 Create a custom program with a selection screen criteria as shown below.

 Put a select query on the table KNA1 and get the value of
KUNNR(Customer), LIFNR (Vendor) into table lt_vendor for KUNNR is equals
to P_KUNNR( selection screen customer).
 Then put a select query on the table BSIK and get the values of required
fields into table LT_BSIK where LIFNR (Vendor) is equals to LT_VENDOR-
LIFNR , BUKRS is equals to P_BUKRS(selection screen company code) and
BUDAT is equals to P_BUDAT(selection screen creation date).
 LT_BSIK contain all the Open Vendor invoices related details.

4 Interface Requirements

4.1 Volume of Data


NA
4.2 Performance Criteria
NA

Page 16of 19
Technical Specification for Pestana

5 Data Conversion Requirements


5.1 Detailed Specification
NA
5.2 Transfer Protocol Details
NA
5.3 Field Mappings
NA
5.4 Volume of Data
NA
5.5 Performance Criteria
NA

Page 17of 19
Technical Specification for Pestana

6 Reporting Requirements
6.1 Detailed Specification
NA
6.2 Reporting Layout
NA
6.3 Reporting Input Screens
NA
6.4 Performance Criteria
NA

Page 18of 19
Technical Specification for Pestana

7 Assumptions, Security and Unit Testing


7.1 Assumptions
NA
7.2 Security
NA
7.3 Unit Test Plan (Internal – Not for Client Review)

Unit Test Plan Target Test Date


MM/DD/YYYY

Page 19of 19

Vous aimerez peut-être aussi