Planvisage Enhancements:

A. In order to overcome the drawback of Planvisage application and for

reporting purpose additional data element to be fetched from SAP as listed
below

1. SapItemMaster :

Field Table Technical name File Name

Net Weight MARA NTGEW SapItemMaster
Production Scheduler MARC FEVOR SapItemMaster
(TA1,TA2, TM1)

Net weight field will be used to identify load in Hedavali Plant.

Production scheduler field will be used to identify Assembly /Component as it

is not possible to have multiple filter in Planvisage.

2. SapBomConsumption:

Field Table Technical name File Name

Line text1 STPO POTX1 SapBomConsumption
Line text 2 STPO POTX2 SapBomConsumption

These fields are required for information purpose also these can be used to
identify scope(Project/ Planning) as these varies from case to case basis
example: Seals & Pipe and fitting items.

3. SapStockTransfer:

Field Table Technical name File Name

MRP Controller EBAN DISPO SapStockTransfer
Purchasing Group EKKO EKGRP SapStockTransfer
Material Group EKPO WGBEZ SapStockTransfer

These fields are required for maintaining of supplier portal data &
monitoring of Stock transfer orders.

B. Storage location wise stock:

Plant stock material is inspected by QA personnel for ongoing projects on
request from Planning and Project department, after inspection no usable
materials are transferred to 3216 storage location. As per current practice
SapInventory text file is generated through MD04 T code through BAPI
MD_STOCK_REQUIREMENTS_LIST_API. As storage location is not available in MD04
screen, processing logic of data download need to be changed.
Standard Program RM07MLBS should be used to fetch storage location wise
stock excluding those storage locations which will be maintained in Z table.
C. Additional text file required for linking reservation against Production Order.
Once production order is created for header scheduling is carried out based
on Production order routing only without considering the availability of child
item.

Field Table Technical name File Name

Reservation Number RESB RSNUM SapResv
Reservation item number RESB RSPOS SapResv
Production order/Planned order RESB AUFNR/PLNUM SapResv
Item number RESB POSNR SapResv
Final issue RESB KZEAR SapResv

Processing Logic: All open reservation against Production order

(Movement Type -261) should be downloaded in new text file from RESB
table

Field Table Technical name File Name

Reservation Number RESB RSNUM SapResv
Reservation item number RESB RSPOS SapResv
Purchase requisition/ Purchase RESB EBELN/BANFN SapResv
Order
Item number RESB EBELP/BNFPO SapResv
Final issue RESB KZEAR SapResv

Processing Logic: All open reservation against sub contracting Purchase

Requisition/ Purchase Order and Line item

D. Enhancement in Requisitioner name:

Requisitioner name is entered in every Purchase requisition by concerned
stake holder, since no validation exist for requisitioner field and many times,
in advertently incorrect data is entered. To overcome this issue
enhancement in PR requisitioner field is required to be carried out where
instead of entering data in requisitioner field data will be selected from Z
table. This will help them to update data in supplier portal requisitioner wise.
(User exist -EXIT_SAPLMEREQ_005 )