0% found this document useful (0 votes)
111 views10 pages

MM - TS - 033 - PR - Buyer Assignment

This document provides technical specifications for assigning a buyer in a purchase requisition. It outlines the requirements, objects affected, development overview including assumptions and dependencies, detailed technical specifications, and testing requirements. The custom development will allow business users to assign a buyer who can take further action on purchase requisitions.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
111 views10 pages

MM - TS - 033 - PR - Buyer Assignment

This document provides technical specifications for assigning a buyer in a purchase requisition. It outlines the requirements, objects affected, development overview including assumptions and dependencies, detailed technical specifications, and testing requirements. The custom development will allow business users to assign a buyer who can take further action on purchase requisitions.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 10

Financial Doc Status

Technical Specification

PR_Buyer assignment

Buyer assignment in Purchase Requisition

Last Updated On: 25 Oct 2014 Page 1 of 10 Version: 1


Financial Doc Status

Document Information

Deliverable Name Buyer assignment in Purchase Requisition


Author Ajay Gulati
SAP Module/Team MM
FS Shivraj Anvikar / Rahul Jain/ Swati Koul
Priority High
Complexity Level Medium
Program Type Report
Version V1.0
Status Completed

Revision History

Version
Date Author Revision Description
No.
V1.0 20/08/2014 Ajay Gulati

Other Related Documents

Related Document Comment


MM_FS_033_PR_Buyer assignment

1 Development Overview

1.1 Requirements Summary

As per the business requirement “The User should be able to assign the buyer” the scope of
This custom development is that the business user should be able to assign the buyer in the
Purchase requisitions for further actions.

Last Updated On: 25 Oct 2014 Page 2 of 10 Version: 1


Financial Doc Status

1.2 Assumptions

1.3 Dependencies / Constraints

1.4 Objects or Transactions Affected

1.5 Transaction Volume

1.6 Standards

1.7 Security, Integrity, and Controls

1.8 Error Messages


Error Number Error Message Corrective Action
001 Records updated Check the value
002 No records selected Check the value
003
1.9 Estimation of Effort

1.10 SAP Objects

Last Updated On: 25 Oct 2014 Page 3 of 10 Version: 1


Financial Doc Status

Name Type Description


Program ZMM_PR_BUYER_ASSIGNMENT_UPDATE
Include
Transaction ZMM_BA
Table
Project
User Exit
BADI Implementation
Method
Implementing class
SAP Script
Adobe Form
Message Class
BOR Object
Workflow Template
Enhc. Implementation

2 Detailed Technical Specifications

2.1 Technical Flow Diagram

2.2 Selection Screen Details

Create selection screen with option to create different parameters and selection ranges
Tables and fields use in selection screen define and screen shot as shown below:

PR_PLANT FOR EBAN-WERKS “Plant


SO_BSTYP FOR EBAN-BSTYP “Purch Doc. Category
SO_BSART FOR EBAN-BSART “Document Type
SO_PR_NO FOR EBAN-BANFN “Purchase Requisition
SO_PR_DT FOR EBAN-BADAT “Requisition Date
PR_TRCNO FOR EBAN-BEDNR “Req. Tracking Number
SO_FRGKZ FOR EBAN-FRGKZ “Release indicator
SO_FRGDT FOR EBAN-FRGDT “Release Date
SO_MT_CD FOR EBAN-MATKL “Material Group
SO_M_CD FOR EBAN-MATNR “Material
PR_REQBY FOR EBAN-AFNAM “Requisitioner
SO_P_GRP FOR EBAN-EKGRP “Purchasing Group
SO_STATU FOR EBAN-STATU “Processing status

Last Updated On: 25 Oct 2014 Page 4 of 10 Version: 1


Financial Doc Status

2.3 Technical Flow Description

1. Create an internal table IT_EBAN and work area WA_EBAN type table of ‘EBAN’

2. Now fetch all the fields from EBAN into internal table IT_EBAN where

Eban~banfn in so_pr_no
Eban~werks in pr_plant
Eban~badat in so_pr_dt
Eban~ekgrp in so_p_grp
Eban~afnam in pr_reqby
Eban~bednr in pr_trcno
Eban~matkl in so_mt_cd
Eban~matnr in so_m_cd
Eban~bsart in so_bsart
Eban~bstyp in so_bstyp
Eban~statu in so_statu
Eban~dispo in so_dispo
Eban~frgkz in so_frgkz

Last Updated On: 25 Oct 2014 Page 5 of 10 Version: 1


Financial Doc Status

3. Create an internal table IT_ZPUR_WF_REM_HIST and work area WA_ZPUR_WF_REM_HIST


Type table of ZPUR_WF_REM_HIST

4. Now fetch all the fields from ZPUR_WF_REM_HIST in to internal table


IT_ZPUR_WF_REM_HIST and check all the value in IT_EBAN where
BANFN = IT_EBAN-BANFN

5. LOOP AT IT_EBAN INTO WA_EBAN

Fetch PTEXT into WA_EBAN-PTEXT from T163Y where SPRAS = SY-LANGU


And PSTYP = WA_EBAN-PSTYP

Now read an internal table IT_ZPUR_WF_REM_HIST and work area


WA_ZPUR_WF_REM_HIST where BANFN = WA_EBAN-BANFN

If condition is true then


WA_EBAN-FRGDT = WA_ZPUR_WF_REM_HIST-BUDAT

Modify IT_EBAN from WA_EBAN

6. Now call the function module to display the output in ALV form and pass the variables and
Internal table as shown below:

Call function 'REUSE_ALV_GRID_DISPLAY'


Exporting
I_callback_program = sy-repid
I_callback_pf_status_set = 'SET_PF_STATUS'
* I_callback_top_of_page = 'TOP-OF-PAGE'
I_callback_user_command = 'USER_COMMAND'
It_fieldcat = fieldcat
Is_layout = gs_layout
Tables
T_outtab = it_eban
Exceptions
Program_error =1
Others =2

2.4 Security and Authorization


To be authorized to the concerned person having right to execute the transaction
2.5 Processing and Operational Considerations

Last Updated On: 25 Oct 2014 Page 6 of 10 Version: 1


Financial Doc Status

2.5.1 Dependencies
NA
2.5.2 Batch Requirements

NA

2.5.3 Restart / Recovery Procedures

2.5.4 Data Maintenance Requirements

2.5.5 Re-use Details

2.5.6 Multi-Company, Multi-Jurisdiction Considerations


N/A

3 Technical Requirements
3.1 Database Tables
NA
3.2 External Programs
NA
3.3 Development Class
ZMMP
3.4 Message Class
NA
3.5 Program ID
NA
3.6 Program Type
NA
3.7 Module
MM
3.8 Transport Number(s)
CR Request Number Task Number

3.9 Detailed Design

3.9.1 SAP Objects


Name Type Transport No. Description
Transaction Code Transaction Code
Executable Program Main Program
Include Program Top Include
Include Program Selection Screen

Last Updated On: 25 Oct 2014 Page 7 of 10 Version: 1


Financial Doc Status

Include Program Processing routine


3.9.2 Request Mechanism / Trigger
NA
3.9.3 Configuration (optional)
NA
3.9.4 Pseudo Code

3.9.5 ABAP Development

3.9.6 Workflow
N/A

3.9.7 Dialog Program


N/A

3.9.8 Custom Table Development


 Table Field Definitions
Field Name Character Key Description
N/A

 Table Validation Rules


Event Form Routine Include
N/A

Last Updated On: 25 Oct 2014 Page 8 of 10 Version: 1


Financial Doc Status

3.9.9 User Exit

3.9.10 Field Exit


N/A

3.9.11 Technical Design Constraints


N/A

3.9.12 Programmer’s Notes

4 Testing Requirements
4.1 Key Unit/Assembly Test Conditions
Unit Test Log
Test Objective

Step Date Description Expected Actual Requirement ID Sign-off


No. Output/Results Output/Results

Notes

5 Outstanding Issues
Issue No Description Assigned To Status Impact Resolution
001
002

5 Appendix
5.1 Glossary of Terms
Term Definition

5.2 Additional Supporting/Reference Documentation

Last Updated On: 25 Oct 2014 Page 9 of 10 Version: 1


Financial Doc Status

5.3 Report Output

Last Updated On: 25 Oct 2014 Page 10 of 10 Version: 1

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy