Scribd
Upload
41 views3 pages

Requirement 1 - PR No. Is Mandatory in PO For Plants 1100,2200,3300

The document describes solutions for two requirements regarding making the PR No. field mandatory for certain document types and plants in purchase order documents in SAP. The first requirement involves making PR No. mandatory for plants 1100, 2200, and 3300. The solution is to create a custom table to store valid plant values and validate the plant entered on a PO matches a value in this table, returning an error if not. The second requirement expands this to additionally require PR No. for document types NB and UB for plants 1100 and 2200. The solution is similar but with a custom table to store valid combinations of plant and document type to validate against when creating a PO. Effort estimates are provided for both solutions

Uploaded by

mahesh Khatal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
41 views3 pages

Requirement 1 - PR No. Is Mandatory in PO For Plants 1100,2200,3300

The document describes solutions for two requirements regarding making the PR No. field mandatory for certain document types and plants in purchase order documents in SAP. The first requirement involves making PR No. mandatory for plants 1100, 2200, and 3300. The solution is to create a custom table to store valid plant values and validate the plant entered on a PO matches a value in this table, returning an error if not. The second requirement expands this to additionally require PR No. for document types NB and UB for plants 1100 and 2200. The solution is similar but with a custom table to store valid combinations of plant and document type to validate against when creating a PO. Effort estimates are provided for both solutions

Uploaded by

mahesh Khatal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Requirement 1 – PR No.

is mandatory in PO for Plants 1100,2200,3300


- User should able to do necessary changes as per requirements
- SAP should show error and not warning

Solution –

1. Create Custom Table/ T code as ZPR_PLANT


2. Selection screen after execution of Custom T code

Execute

Plant To (Multiple Selection)

3. Execution Screen

Plant Description

- Validation – Pick plant from custom T code ZPR_PLANT and pass it to table
T001W-WERKS , If entry does not exist in table T001W-WERKS then show error
as “Plant does not exist in TOO1W”

4. Plant Field Length - 4


5. Plant Field name - WERKS
6. Date type – CHAR
7. Validation while Creation of PO – Pick plant from PO Creation screen and pass it to custom
table / T code ZPR_PLANT to check if plant is exist or not and if plant is exist & PR no. field in
PO is blank then show error as “PR No. is Mandatory”

Effort Estimation –
Efforts Functional Technical
(1 Man Hrs./day) (1 Man Hrs./day)
Configuration/ Logic 2 3
Unit testing 0.5 0.5
UAT 0.5 0
UT Document 0.5 0.5
User Manual 1 0
TR Movement 1 0
Batch job 0 0
Total 5.5 4.5
Requirement 2 – PR No. is mandatory in PO but this is applicable for PO Doc. Type NB, UB
And Plants 1100,2200
- User should able to do necessary changes as per requirements
- SAP should show error and not warning

Solution –

1. Create Custom Table/ T code as ZPR_DOC_PLANT


2. Selection screen after execution of Custom T code

Execute

Plant To (Multiple Selection)

Doc Type To (Multiple Selection)

3. Execution Screen

Plant PR No. Doc Type PR No.

Validation –

- Pick Document Type from custom T code ZPR_DOC_PLANT and pass it to table
T161-BSART-BSTYP, if entry does not exist in table T161- BSART-BSTYP then
show error as “Doc. Type does not exist in T161”
- Pick Plant from custom T code ZPR_DOC_PLANT and pass it to table T001W-
WERKS, if entry does not exist in table T001W-WERKS then show error as “Plant
does not exist in TOO1W”

4. Field Length –
a. Doc. Type -4
b. Plant -4
5. Field name –
a. Doc. Type - BSART
b. Doc. Category - BSTYP
c. Plant - WERKS
6. Date type –
a. Doc. Type - CHAR
b. Plant - CHAR
7. Validation while Creation of PO – Pick Doc. Type & plant from PO Creation screen and pass it
to custom T code ZPR_DOC_PLANT to check if Doc. Type & plant is exist or not and if Doc.
Type & plant is exist & PR no. field in PO is blank then show error as “PR No. is Mandatory”

Effort Estimation –
Efforts Functional Technical
(1 Man Hrs./day) (1 Man Hrs./day)
Configuration/ Logic 2 4
Unit testing 0.5 0.5
UAT 0.5 0
UT Document 0.5 0.5
User Manual 1 0
TR Movement 1 0
Batch job 0 0
Total 5.5 5

You might also like