TS INC000001669794 - V2P PR line item deletion issue.doc

Technical Specification

Filename:

document.doc

Page 1 of 26

Technical Specif icat ion

Version Control

Version Date Comment/Changes Project or Change Request Number

Completed By

1.0 25th March 2013 Initial draft version 552105 MARSX557

1.1 24th April 2013 Validation for Line Item Data 552278 MARSX557

1.2 17th May 2013 Not to proceed with Validation if PR is not saved (Line Item table is empty)

552386 MARSX557

Purpose of documentThe purpose of this document is to provide technical design and scope for developing ABAP object(s) and Web applications. This will serve as an input to the developer before he undertakes the development; therefore all the relevant sections of this document should be completed. This document will also be used by the Service Delivery team for supporting the systems and therefore it should be kept up-to-date.

AudienceDevelopment teams, Solution Architecture team, and Service Delivery team.

File Naming Convention

Technical Specs:

Purchase Requisition Validation

Do not store version numbers in the filename. We will now have a living master document and see section 4.2 for instructions on how to see version history.

document.doc Page 2 of 26


Table of Contents1 Development Summary.......................................................................5

2 Scope Summary...................................................................6

2.1 Development Summary...............................................................................................................6

2.2 Development Objects per System................................................................................................6

2.3 Reference Programs.................................................................................................................... 6

2.4 Dependency on Other Development or Interface.........................................................................6

3 Development Scope.............................................................7

3.1 Generic Solution Details..............................................................................................................7

3.1.1 Configuration....................................................................................................................................7

3.1.2 Authorizations...................................................................................................................................7

3.1.3 Message Class and Messages.........................................................................................................7

3.1.4 Selection Screen...............................................................................................................................7

3.1.5 Data Object.......................................................................................................................................7

3.1.6 Input Format.....................................................................................................................................8

3.1.7 Output Format...................................................................................................................................8

3.1.8 Output Medium.................................................................................................................................8

3.1.9 Output Layout Details / Sample Formats..........................................................................................9

3.1.10 Screen code .....................................................................................................................................9

3.1.11 Screen layout..................................................................................................................................10

3.1.12 Screen Field Definition....................................................................................................................10

3.1.13 Menu implementation.....................................................................................................................10

3.1.14 Screen Sequence...........................................................................................................................10

3.1.15 Business Logic................................................................................................................................11

3.1.16 Run Mode.......................................................................................................................................11

3.1.17 Error Handling.................................................................................................................................113.2 Specific Solution Details............................................................................................................12

3.2.1 BADI...............................................................................................................................................12

3.2.2 BTE.................................................................................................................................................12

3.2.3 Customer-Exits (CMOD).................................................................................................................12

3.2.4 User-Exit Routines..........................................................................................................................13

3.2.5 Copy Routines................................................................................................................................13

3.2.6 BSP Template Enhancement.........................................................................................................14

3.2.7 CRM Middleware Development......................................................................................................14

3.2.8 Function Module / RFC / BAPI........................................................................................................14

3.2.9 SAP XI – ABAP Proxy Development..............................................................................................16

3.2.10 Class / Interface Development........................................................................................................16

3.2.11 IDOC Development.........................................................................................................................16

3.2.12 FTP scripting requirements.............................................................................................................19

3.2.13 Bespoke Table................................................................................................................................19



3.2.14 Search helps...................................................................................................................................20

3.2.15 Lock Objects...................................................................................................................................21

3.2.16 Number Range Objects..................................................................................................................213.3 BW Extractors............................................................................................................................ 21

3.4 Portal / Java Developments.......................................................................................................21

3.4.1 General...........................................................................................................................................21

3.4.2 Portal iView.....................................................................................................................................21

3.4.3 Server-side Development...............................................................................................................21

3.4.4 Client-side Development.................................................................................................................22

3.4.5 Business Logic................................................................................................................................22

3.4.6 BAPIs Used....................................................................................................................................22

3.4.7 Authorizations.................................................................................................................................22

3.4.8 Error Handling.................................................................................................................................22

3.4.9 Branding Requirements..................................................................................................................23

3.4.10 Compilation.....................................................................................................................................23

3.4.11 Deployment.....................................................................................................................................23

3.4.12 Screen Sequence...........................................................................................................................23

3.4.13 Screen layout..................................................................................................................................23

3.4.14 Field Definition................................................................................................................................233.5 CRM Field Sales developments.................................................................................................24

3.6 Actions....................................................................................................................................... 24

4 Other Considerations / Impacts..........................................25

4.1 Important Comments/Considerations.........................................................................................25

4.2 Performance Considerations......................................................................................................25

4.3 Volume of Data (Cut over consideration)...................................................................................25

4.4 Line of Business Specific Considerations..................................................................................25

4.5 Language Considerations..........................................................................................................25

4.6 Sarbanes Oxley Considerations.................................................................................................25

4.7 Cross Work Stream Impact........................................................................................................25

4.8 Regression Impacts...................................................................................................................25

4.9 Archiving Compatibility...............................................................................................................25

5 Unit Test...........................................................................26

5.1 Unit Test Specification...............................................................................................................26

5.2 Test Data or Sample file............................................................................................................26

6 Glossary.............................................................................................27



1 Development Summary

Business Criticality: High

Development Model : Standard

Type : Enhancement

Note

Please do not delete or leave any section blank; put N/A if a section is not applicable.



2 Scope Summary

2.1 Development Summary

When a purchase requisition is created for indirect procurement it is subject release strategy. Only upon release of PR, PO creation is allowed. PR approval process is subject audit and has defined approval processes. This enhancement is to fill the gaps where the standard system is lacking. This will ensure compliance to audit requirements.

2.2 Development Objects per SystemS.No System Package Development

ObjectDescription

1 ECC ZDPS_V2P COST_CENTER_VALIDATION1 Method

2.3 Reference Programs

S.No System Development Object

Type (Copy or Call)

Description

N/A N/A N/A N/A N/A

2.4 Dependency on Other Development or Interface

N/A



3 Development Scope

3.1 Generic Solution Details

3.1.1Configuration

Area Description Config/Reqs Comments

Webservice Protocol N/A

Security requirement N/A

Anonymous Login details N/A

Authentication N/A

SAP Trans - XXnn N/A

3.1.2Authorizations

N/A

S.No Authorization Object Authorization Object Field SAP field1

N/A N/A N/A2

3.1.3Message Class and Messages

S.No Message Class

Message Number

Short Text Long Text

N/A N/A N/A N/A N/A

3.1.4Selection Screen S – Select Option P – Parameter

S.No Field Name S or P Mandatory Comments

1 N/A N/A N/A N/A

3.1.5Data Object

System Data object

Table or other data source (Function, LDB etc)

Main fields Comments

CRM N/A N/A N/A

SAP N/A N/A N/A



3.1.5.1 Business Logic for Data Retrieval

Data Object Foreign Keys and/or access rules

Comments

N/A N/A N/A

3.1.6 Input Format

Level 1

S.No Field Name Comments

N/A N/A N/A

3.1.7Output Format

Level 1

S.No Field Name Comments

N/A N/A N/A

3.1.8Output Medium

Item Online

(List Report, ALV etc)

Print (width, 80, 132 etc)

DMS Other – Fax, Fiche, Telex etc

Special Requirements

(Bulk printing, Envelope stuffing, Retained output

N/A N/A N/A N/A N/A N/A

3.1.9 Output Layout Details / Sample FormatsN/A



3.1.10Screen code . N/A

Transaction Code, iView etc N/A Transaction Text N/A Transaction Attribute selected N/A Technical description N/A Authorization details N/A

Multi-User Access Consideration N/A

Branding RequirementsN/A

3.1.11Screen layout

Screen Identification: N/A Screen Number: N/A

N/A

3.1.12Screen Field Definition

Screen Identification Screen Number

Field Name Description Size Attributes Format Validation, Error actions


3.1.13Menu implementation

Menu Identification Menu Code

Function Key Button Label Menu Label Processing Module Name

N/A N/A N/A N/A N/A

3.1.14Screen SequenceN/A



3.1.15Business Logic

Check IF ls_head-estkz = 'R' OR ls_head-estkz = 'F'. If yes then check whether IM_ITEM-AKTYP = ‘V’ (Change). If yes then get IM_ITEM-BANFN and IM_ITEM-BNFPO.

Select PR Number, Item Number of PR, Account Assignment Category and Purchasing Group from EBAN table by where PR No is equal to IM_ITEM-BANFN and Item no of PR is equal to IM_ITEM-BNFPO.

SELECT banfn bnfpo knttp ekgrp FROM eban INTO TABLE lt_eban WHERE banfn = lv_banfn AND bnfpo = lv_bnfpo.

Select PR Number, Item Number of PR, Order Number and Cost Center from EBKN table where PR No is equal to IM_ITEM-BANFN and Item no of PR is equal to IM_ITEM-BNFPO.

SELECT banfn bnfpo aufnr kostl FROM ebkn INTO TABLE lt_ebkn WHERE banfn = lv_banfn AND bnfpo = lv_bnfpo AND zebkn IN lr_zebkn.

Select Order Number, Order category, Responsible Cost Center, Settlement cost element from AUFK table for all entries in Internal Table of EBKN where order no is present.

SELECT aufnr autyp kostv kstar FROM aufk INTO TABLE lt_aufk1 FOR ALL ENTRIES IN lt_ebkn WHERE aufnr = lt_ebkn-aufnr.

Select Order Number, Order category, Responsible Cost Center, Settlement cost element from AUFK table where Order Number is equal to ls_acdata-aufnr.

SELECT aufnr autyp kostv kstar FROM aufk INTO TABLE lt_aufk WHERE aufnr = ls_acdata-aufnr.

Get Header for Requisition and Data For Line Item

ls_header = im_item->get_requisition( ).ls_head = ls_header->get_data( ).lt_item = ls_header->get_items( ).



ls_info = ls_item-item->get_data( ).

Version 1.1

Deleted all those items from lt_item which are not present in im_item before looping at lt_item.

DELETE lt_item WHERE item NE im_item.

End of Version 1.1

Version 1.2

Check whether the internal table for PR line items contains any data or not. If lt_item is blank, then do not proceed with the validations and exit from the method else continue. (lt_item table will be initial if the PR is not saved).

CHECK lt_item IS NOT INITIAL.

End of Version 1.2

Approval Based on Purchasing Group Logic

IF ls_info-knttp is initial or ‘U’ and ls_info-frgzu is not initial and ls_info-loekz is initial then read the internal table of EBAN where PR Number is equal to im_item-banfn and Item no of PR is equal to im_item-bnfpo. If ls_info-knttp <> lw_eban-knttp or ls_info-ekgrp <> lw_eban-ekgrp, display error message “Changing of Purchasing Group or account assignment field for PR approvals based on purchasing group not allowed after approval”.

Approval Based on Cost Center Logic

IF ls_info-knttp = ‘K’ and ls_info-frgzu is not initial and ls_info-loekz is initial, then read the internal table of EBAN where PR Number is equal to im_item-banfn and Item no of PR is equal to im_item-bnfpo.

If ls_info-knttp <> lw_eban-knttp or ls_info-ekgrp <> lw_eban-ekgrp, display error message “Changing of Cost Center or account assignment field for PR approvals based on cost center not allowed after approval”; Else read internal table of EBKN where PR Number is equal to im_item-banfn and Item no of PR is equal to im_item-bnfpo. IF lw_ebkn-kostl is not equal to ls_acdata-kostl display error message “Changing of Cost Center or account assignment field for PR approvals based on cost center not allowed after approval”.

Approval Based on Order Logic

If ls_info-knttp = ‘F’ OR ‘R’ and ls_info-frgzu is not initial and ls_info-loekz is initial, then read the internal table of EBAN where PR Number is equal to im_item-banfn and Item no of PR is equal to im_item-bnfpo.

Read internal table of AUFK where Order number is equal to ls_acdata-aufnr. Read internal table of of EBKN where PR Number is equal to im_item-banfn and Item no of PR is equal to im_item-bnfpo. IF read on internal table of EBKN is successful then read internal table of AUFK again where Order Number is equal to lw_ebkn-aufnr.



If previous account assignment is not equal to F and R then throw error “Changing of orders only allowed when approving cost center is same or change in account assignment field for PR approvals based on orders not allowed after approval”.

Else; If Order type in Internal Table of AUFK is 01 or Order Type is 30 and Settlement Cost Center is Initial then check whether the Order type in Internal Table of AUFK1 is 01 or Order Type is 30 and Settlement Cost Center is Initial. If Responsible cost center of AUKF is not equal to that of AUFK1, then throw error “Changing of orders only allowed when approving cost center is same or change in account assignment field for PR approvals based on orders not allowed after approval” else if Settlement Cost Center of Internal table of AUFK1 is not equal to Responsible Cost Center of AUFK, throw error “Changing of orders only allowed when approving cost center is same or change in account assignment field for PR approvals based on orders not allowed after approval”.

Else; If Order type in Internal Table of AUFK1 is 01 or Order Type is 30 and Settlement Cost Center is Initial; if Settlement Cost Center of Internal table of AUFK is not equal to Responsible cost center of AUFK1, throw error “Changing of orders only allowed when approving cost center is same or change in account assignment field for PR approvals based on orders not allowed after approval”.

Else if Settlement Cost Center of Internal table of AUFK is not equal to Settlement Cost Center of AUFK1, throw error “Changing of orders only allowed when approving cost center is same or change in account assignment field for PR approvals based on orders not allowed after approval”.

If Account Assignment Category in Internal Table of EBAN is equal to ‘F’ or ‘R’ and Account Assignment Category of ls_info is not equal to ‘F’ or ‘R’ then check if Order type in Internal Table of AUFK is 01 or Order Type is 30 and Settlement Cost Center is Initial then check whether the Order type in Internal Table of AUFK1 is 01 or Order Type is 30 and Settlement Cost Center is Initial. If Responsible cost center of AUKF is not equal to that of AUFK1, then throw error “Changing of orders only allowed when approving cost center is same or change in account assignment field for PR approvals based on orders not allowed after approval” else if Settlement Cost Center of Internal table of AUFK1 is not equal to Responsible Cost Center of AUFK, throw error “Changing of orders only allowed when approving cost center is same or change in account assignment field for PR approvals based on orders not allowed after approval”.

Else; If Order type in Internal Table of AUFK1 is 01 or Order Type is 30 and Settlement Cost Center is Initial; if Settlement Cost Center of Internal table of AUFK is not equal to Responsible cost center of AUFK1, throw error “Changing of orders only allowed when approving cost center is same or change in account assignment field for PR approvals based on orders not allowed after approval”.

Else if Settlement Cost Center of Internal table of AUFK is not equal to Settlement Cost Center of AUFK1, throw error “Changing of orders only allowed when approving cost center is same or change in account assignment field for PR approvals based on orders not allowed after approval”.

3.1.16Run ModeForeground

3.1.17Error HandlingN/A



3.2 Specific Solution Details

3.2.1BADI

SAP Transaction ME51N, ME52N, ME53N

Implementation Name Z_PR_COST_VALIDATION

Definition Name ME_PROCESS_REQ_CUST

Multiple Use No

Filter No

Method Name COST_CENTER_VALIDATION1

Input / Output Data IM_ITEM Type Ref To IF_PURCHASE_REQUISITION_ITEMIM_COUNT Type IIM_REF_ITEM Type Ref To IF_PURCHASE_REQUISITION_ITEM

Business Logic N/A

Error Handling N/A

3.2.2BTE

SAP TransactionN/A

Type of BTEN/A

BTE Number / DescriptionN/A

Function Module NameN/A

Configuration DataN/A

Error Handling N/A

3.2.3Customer-Exits (CMOD)

SAP TransactionN/A

SMOD NameN/A

CMOD project NameN/A

Component N/A

Input / Output DataN/A



Business LogicN/A

Error HandlingN/A

3.2.4User-Exit Routines

Name of the RoutineN/A


Business LogicN/A

Error HandlingN/A

3.2.5Copy Routines

Configuration StepsN/A

Name of the RoutineN/A


Business LogicN/A

Error HandlingN/A

3.2.6BSP Template Enhancement

Configuration StepsN/A

URLN/A

Name of the ServiceN/A

ThemeN/A

HTML Template NameN/A

Change DetailsN/A

Error HandlingN/A

3.2.7CRM Middleware Development

BDOC Name N/A

Type N/A

Related Data type N/A

Mode N/A

Implementing Class N/A



3.2.8Function Module / RFC / BAPI

Function Module Nam N/A

Function Module Text N/A

Type of Function Module N/A

Function Group N/A

Business Object N/A

Authorization N/A

Import , Export, Changing Parameters

Field Name Reference Type

Default Value

Import/ Export/ Changing Parameter

Comments

N/A N/A N/A N/A N/A

Table Parameters

Field Name Reference Type Comments

N/A N/A N/A

Exceptions

Exceptions Short Text Comments

N/A N/A N/A

Business LogicN/A

Error HandlingN/A

Documentation N/A



3.2.9SAP XI – ABAP Proxy Development

Type N/A

Name N/A

Short text N/A

Direction N/A

Mode N/A

Proxy Interface N/A

Implementing Class N/A

3.2.10Class / Interface DevelopmentClass Name/ Interface

N/ASuper Class

N/AInterface Name

N/A

Method NameN/A


Business LogicN/A

Error HandlingN/A

3.2.11IDOC Development

3.2.11.1GeneralOverall Function Triggering

N/AWhen is the IDoc Triggered

N/AWhen is the IDoc created

N/ABatch or On-line

N/A

3.2.11.2IDoc CustomizingAdditional segment(s)

N/ASegment Name

N/A

3.2.11.3Record Layout

No. Field description Type Len Pos Remarks





3.2.11.4Extension

Extension Name N/A

Linked basic Type N/A

Parent Segment N/A

Mandatory N/A

Minimum Number N/A

Maximum Number N/A

3.2.11.5IDoc Type

IDoc Type name N/A

3.2.11.6Message Type

Message Type Name N/A

Basic IDoc Type N/A

Extension N/A

3.2.11.7Logical System

Logical System Name N/A

3.2.11.8Process Code

Process Code N/A

Basic IDOC Type N/A

Message Type N/A

Function Module N/A

3.2.11.9Distribution Model

Model View N/A

Sender/Client N/A

Receiver/Server N/A

Message type N/A

3.2.11.10 Transactional RFC Port

RFC Destination Name N/A

Connection Type N/A

3.2.11.11 File Port

Port Name N/A

Directory N/A

File Name N/A



Function Module N/A

3.2.11.12 XML File port

Outbound File

Port Name N/A

Directory N/A

File Name N/A

Function Module N/A

Send DTD N/A

Convert Special Character N/A

Outbound Trigger

Automatic Start N/A

RFC Destination N/A

File Name(Logical / Physical) N/A

3.2.11.13 XML HTTP

Port Name N/A

RFC Destination N/A

Content type N/A

SOAP Protocol N/A

3.2.11.14 Partner profile

Partner Number N/A

Partner Type N/A

3.2.11.15 Inbound/outbound Parameters

Output Mode N/A

Port N/A

Package Size N/A

Process Immediately N/A

Collect IDOCs N/A

3.2.11.16 Message Control

Application N/A

Message (output) Type N/A

Logical Message Type N/A

Process Code N/A

Condition Record N/A

3.2.11.17 IDoc Processing

N/A



3.2.11.18 ABAP Processing

N/A

3.2.11.19 Description of Output



3.2.11.20 Programs/function modules for creation of IDOCs

N/A

3.2.11.21 Error handling for inbound/outbound (link to any workflow developments)

N/A

3.2.12FTP scripting requirements

N/A

3.2.13Bespoke Table

Table Name N/A

Short text N/A

Data Class N/A

Maintenance N/A

Transaction N/A

Authorization group for table N/A

Table size N/A

Buffering N/A

N/A

Log Data Changes N/A

Client independent table N/A

Field name

Key Data Elemt. Or type/length

Short text Check Table Comments, F1 help, special display, …




3.2.13.1Structures / Table Types

Table Type name N/A

Structure name N/AField name


Short text Check Table Comments, F1 help, special display, …


3.2.13.2Data ElementsS.No Data

ElementDomain Description(s) Comments

N/A N/A N/A N/A N/A

3.2.13.3DomainS.No Field

TypeFieldLength

Value table/Fixed Values Comments

N/A N/A N/A N/A N/A

3.2.13.4Table Maintenance Enhancement N/A

3.2.13.5TransactionN/A

3.2.14Search helps

Search Help Name N/A

Short text N/A

Search type Elementary / Collective

Data Source Online maintenance desired: (Y / N)

Search Fields N/A

Output and Selectable fields N/A



3.2.15Lock Objects

Lock Object N/A

Short text N/A

Lock Mode N/A

Primary Tables N/A

Secondary Tables N/A

Lock Parameters N/A

3.2.16Number Range Objects

Number range object N/A

Short text N/A

To Year Flag N/A

Number Length domain N/A

Warning % N/A

Main Memory buffering N/A

3.3 BW Extractors

Configuration N/A

Data Objects N/A

Business Object N/A

Error Handling N/A

Additional Info N/A

Comments N/A

3.4 Portal / Java Developments

3.4.1GeneralN/A

3.4.2Portal iViewN/A

3.4.3Server-side DevelopmentN/A

3.4.3.1 Enterprise Java BeansN/A

3.4.3.2 Java Messaging ServicesN/A



3.4.3.3 Database ConnectivityN/A

3.4.3.4 Portal ServicesN/A

3.4.3.5 SAP Java ConnectorN/A

3.4.3.6 Web ServicesN/A

3.4.4Client-side DevelopmentN/A

3.4.5Business LogicN/A

3.4.6BAPIs UsedN/A

3.4.6.1 BAPI List

3.4.6.1.1 Corresponding Java Classes (BAPI Wrappers / Proxies)

3.4.6.2 Structures / Table Types

Table Type name N/A

Structure name N/A

Java Class name N/AField name


Decription Java Field Java type


3.4.6.3 Data ElementsS.No Data

ElementDomain Description(s) Comments

N/A N/A N/A N/A N/A

3.4.7AuthorizationsN/A

3.4.8Error HandlingN/A

3.4.9Branding RequirementsN/A

3.4.10CompilationN/A



3.4.11DeploymentN/A

3.4.12Screen SequenceN/A

3.4.13Screen layout


N/A

3.4.14Field Definition


Field Name Description Size Attributes Format Validation, Error actions


3.5 CRM Field Sales developmentsTBC

3.6 ActionsTBC



4 Other Considerations / Impacts

4.1 Important Comments/ConsiderationsN/A

4.2 Performance ConsiderationsN/A

4.3 Volume of Data (Cut over consideration)N/A

4.4 Line of Business Specific Considerations N/A

4.5 Language ConsiderationsN/A

4.6 Sarbanes Oxley ConsiderationsN/A

4.7 Cross Work Stream ImpactN/A

4.8 Regression Impacts N/A

4.9 Archiving CompatibilityN/A



5 Unit Test

5.1 Unit Test Specification

Step Step Description Expected Results Comments

Test Case Description - Purchasing group for non-account assigned PR’s.

1 PR No 2200017361 System behaved as expected. Threw error when purchasing group was changed after release of PR.

2

3

4

Test Case Description - Cost centre for PR’s with account assignment “K”

1 PR No 2200017574 System behaved as expected. Threw error when the cost center was changed after the release of PR.

2

3

Test Case Description - Settlement cost centre for all other maintenance orders.

1 PR No 2200017578 System behaved as expected. Threw error when the cost center was changed after the release of PR.

2

5.2 Test Data or Sample fileN/A



6 Glossary

GT – Global Table

GV – Global Variable

GV – Global Constant

GR – Global Range

LT – Local Table

LV – Local Variable

LV – Local Constant

LR – Local Range


Date post:	03-Jan-2016
Category:	Documents
Upload:	nikhil4133
View:	19 times
Download:	3 times

TS INC000001669794 - V2P PR line item deletion issue.doc

Documents