FS NMIPL MM-05-201-02 Ver221.0

NMIPL After Sales Parts System Project
Solution ID
MM-05-201
Solution Name
Function ID
Inbound Inventory Information Receive

MM-05-201-02
Development Title
Inbound Inventory Information Receive
Project
NMIPL_AS
Team
MM
All Rights Reserved, Copyright NISSAN MOTORS CO., LTD.
Document Preparation and Approval Page
Prepared By:
The Prepared By signature indicates the individual(s) who authored this document:
Prepared By
Name
Title/Role
Kazuya Sakamoto
MM
Reviewed By:
The Reviewed By signature indicates the individual(s) who reviewed this document for content and
clarity, and to the best of their knowledge, this document satisfactorily achieves the purpose and scope
defined herein:
Name
Title/Role
Reviewed By
Masanobu Iwabuchi
Outsource (Application)
Reviewed By
Hiroyuki Mochida
Outsource (Application)
Approved By:
The Approved By signature indicates the individual(s) who approved this document for content and
clarity, and to the best of their knowledge, this document complies with corporate policies and
procedures:
Name
Title/Role
Approved By
Keiji Matsuzaki
Nissan Biz (EAS)
Approved By
Hiroki Murase
Nissan Biz (R40)
Approved By
Tamie Akimori
Nissan IS (BA)
Approved By
Yousuke Matsuoka
Nissan IS (IS)
TABLE OF CONTENTS
1
Objectives....................................................................................................... 4
1.1
Purpose of the Document............................................................................................... 4
Summary......................................................................................................... 5
2.1
Requirement Overview................................................................................................... 5
2.2
Development Type.......................................................................................................... 6
2.3
Impacted Systems.......................................................................................................... 6
2.4
Change Management Considerations/Users and Volumes..............................................6
2.5
Risks/ Issues................................................................................................................... 6
2.6
Dependencies................................................................................................................. 6
Process................................................................................................................. 8
2.7
Process Description........................................................................................................ 8
2.8
Process Flow................................................................................................................. 39
2.9
Systems Referred To..................................................................................................... 40
2.10 Processing Options....................................................................................................... 40

2.11 Security Requirements.................................................................................................. 40
3
Interface/Conversion Information....................................................................41
3.1
Integration Point Overview........................................................................................... 41
3.2
Summary...................................................................................................................... 41
3.3
Dependencies/Prerequisites.......................................................................................... 41
3.4
Interface Information.................................................................................................... 42
3.5
Legacy/External Systems Involved................................................................................42
3.6
Functional Data Map..................................................................................................... 43
3.7
Selection Screen (if applicable).....................................................................................43
3.8
Exception Handling Rules............................................................................................. 43
3.9
Impact on Legacy Systems........................................................................................... 43
3.10 SAP Transaction (Interface that create data in SAP)......................................................43

3.11 Reference Tables........................................................................................................... 44
3.12 Additional Information.................................................................................................. 44
4
Revision History............................................................................................. 45
Objectives
1.1
Purpose of the Document
The objective of the Functional Specification is to provide an overview of the Add-On process and highlight
critical activities that are essential to a successful Add-On.
The document consists of three major sections:
Summary (Section 2)
Process (Section 3)
Interface/ Conversion Information (Section 4)
Summary
2.1
Requirement Overview
2.1.1 Overview
3PL SAP
SAP
2.1.1 Overview
Receive the Inbound/Inventory Information from 3PL, based on the information received, SAP will then
operate the inbound and inventory process in order to reflect the result to SAP. Target items will be
Purchase Order (Domestic, Import, Buyback), Stock Transfer (Referral, Replenishment), Return
Goods. For each item, operate the inbound and inventory process: Inventory process will manage the
quantity of the products that are yet to be included in the inventory. If the inventory quantity exceeds
the inbound quantity, then output as an error.
And if actual receiving quantity (105) is less than delivery instruction quantity (103), system should
reverse the imbalanced quantity of delivery instruction quantity (104) then inbound process should
process (105).
If the material data, purchase order data is not able to change, and the Inbound/Inventory process
turns out as an error, this process will be automatically set to be re-processed for the next time.
2.1.2 Frequency
2.1.2 Frequency
Daytime Process
1 time/30 minutes
2.1.3 Data Scope
N/A
2.1.4 Generate Format
N/A
2.2
Development Type
Development Type:
2.3
( ) Report
( X ) Interface
( ) Form
( ) Workflow
( ) Enhancement
Impacted Systems
Software Package
( X ) SAP ERP
or Business:
( ) BW
( ) SAP SCM
( X ) Legacy System
( ) Tax Software ( ) CRM
( ) Middleware
2.4
( ) Conversion
( ) EDI Sub-System
( ) Portal
( ) Other
Change Management Considerations/Users and Volumes
2.4.1 Change Management Considerations

N/A
2.4.2 Users
JOB
2.4.2 Users
User training is unnecessary because the process is done thru JOB
2.4.3 Volume
2.5
Risks/ Issues
Table
There is a risk in data mismatch, from maintenance leakage on the code conversion table.
2.6
Dependencies
SAP
Supplier
Table
Make sure to have the purchase order (destination to SAP), and Inbound Order to be inserted.
Make sure to have the proper information to be included for the inbound information in order to link. (Insert
the Inbound order based from the Shipping Record which came from the Supplier)
Make sure to check parameter table (ZASG1XXT001) SAP_VAL = LOCAL then system should check,
actual receiving quantity (105) with delivery instruction quantity (103) in NMIPL to aviod job failure.
Make sure to register the necessary code conversion value to the code conversion table.
Process
2.7
Process Description
0.1 MIGO EXIT

Finished Goods Raw Materials Excise Action Part1
EXIT
Part1 Register
0.1 Goods Movement Document EntryMIGO Exit Addtion
When entering the goods receipt, the attributes for the goods receipt materials has to be changed from Finished
Goods to Raw Material and the Excise Action has to be changed to Only Part1. This will be accomplished using
an enhancement implemention.
When entering the goods receipt using the function module, the Part1 Register needs to be updated.
1 Finished Goods(Raw Materials)
2 Excise Action 01(Capture & Post Excise Invoice) 05(Part 1)
1) When entering the goods receipt transaction, the attributes of the goods receipt material has to changed from
Finished Goods to Raw Material.
2) The Excise Action within the goods document header has to be changed from 01 (Capture & Post Excise
Invoice) to 05 (Only Part 1).
The following logic has to be processed
Exit
FUNC_AREAMM
PROJAS
LOCATG1
LEG_SYS3PL
FUN_ID0520102
CONV_OBPLANT
Obtain from the parameter table which plant is to be processed by the enhancement implementation
(Multiple Entries
Search Condition
Parameter TableFUNC_AREAMM
Parameter TablePROJAS
Parameter TableLOCATG1
Parameter TableLEG_SYS3PL
Parameter TableFUN_ID0520102
Parameter TableCONV_OBPLANT
OK
Incoming Excise Invoice CAPIND() ORIG_CAPIND()(

)
Goods Movement Line Item Change Conditions
Condition 1 When the goods movement line item plant is the same as the plant obtained from the
parameter table.
Condition 2 When the [Item OK] flag is set
Condition 3 When the transaction type for goods movement document is other than Display and Cancel.
The following process needs to be executed
The CAPIND(Material attributes) and ORIG_CAPIND(Material attributes) of the internal table Incoming
Excise Invoice has to be set to blank(Raw Materials).

Excise Invoice Header
105 ON
Goods Movement Header Change condition

Condition 1 When the Excise Invoice Header internal table plant is the same as the plant obtained from
the parameter table.
Condition 2 When the goods movement transaction type is goods receipt (Mvt Type:105) and the Plant
Flag is on and when in the posting mode.
Condition 3 When the goods movement transaction type is not Others

Set the Excise Action of the Excise Invoice Header Internal Table to 05(Only Part 1)

Excise Invoice Header
Goods movememt screen refresh

Condition 1If the plant in the Excise Invoice Header is the same as the plant obtained from the parameter
table

The goods movement screen refresh needs to be executed
0.2 EXIT
CVD Clearing Account
CVD Condition Type A/P ECS Condition Type A/P Imports ADC Condition
Type A/P KWERT,KWRFW
J1CV
KWERT,KWRFW
0.2 Goods Movement Document EntryFunction ModuleGoods Movement Exit Addtion
Upon entering the inbound goods receipt, planned delivery costs for CVD Clearing Accounts need to be set to zero.
The following procedure needs to be executed.
1) If the movement type of the goods receipit item and the plant is the same as the values in the parameter table, the
following procedure is executed.
2) Obtain the tax calculation prcedure from the company code.
10
3) Using the tax calculation procedure, the the planned delivery cost condition type is the same as tax calculation
procedure CVD Condition Type A/P or ECS Condition Type A/P Imports or ADC Condition Type A/P, the planned
condition cost (KWERT, KWRFW) needs to be set to zero
4) If the planned delivery condition type is J1CV, the planned delivery cost (KWERT, KWRFW) needs to be set to
zero
1. Add-On
F/#=11
DATA =A10A20U10U20V10N30
Add-On D or C
( EError)
Add-On =
1. Inbound Process: Extract target data from the Add-On Table (Purchase Order/Stock Transfer)
Extract the following data:
Item F/#=11
DATA Segment=A10A20U10U20V10N30
Add-On Table: Status(D or C)
(When Status=E (Error), then set as re-processing item)
Add-On Table: Status = Value fetched from the Screen
1.1
Add-On =EKKOEBELN
Add-On =EKPOEBELP
Add-On No.=EKPOBEDNR
Add-On No.Add-On X
OK
1.2
NG
1.1 Order Existence Check
Add-On Table: Purchase Number=EKKO: EBELN
Add-On Table: Purchase Item Number=EKPO: EBELP
Add-On Table: Issue No.=EKPO: BEDNR
Add-On Table: Issue No.Add-On Table: Deletion Flag: X

OK
Go to 1.2
11
NG
Go to 5 error process
1.2
Add-On =EKKOEBELN
Add-On =EKPOEBELP
EKPOELIKZX
OK
1.3
NG
1.2 Inbound Check for corresponding Order Number

Add-On Table: Purchase Number=EKKO: EBELN
Add-On Table: Purchase Item Number=EKPO: EBELP
Delivery Completion Segment (EKPO: ELIKZ)X
OK
Go to 1.3
NG
1.3
Add-On =EKESBSART
Add-On =EKESEBELP
EKESVBELN
EKESVBELP
OK
1.4
NG
1.3 Existence Check for Inbound Order

Add-On Table: Purchase Number=EKES: BSART
Add-On Table: Purchase Item Number=EKES: EBELP
Inbound Order Number (EKES: VBELNBLANK
Inbound Order Item (EKES: VBELP)BLANK
OK
Go to 1.4
NG
1.4
CASEEKKOBSART=UBZUB
Add-On EKPO:MENGE-EKBE
BWART=103104 EKBEWESBS
NG
12
Add-On <= EKPO:MENGE-EKBE

BWART=103104 EKBEWESBS
OK
1.5
1.4 Quantity Check

CASE For all items except EKKO: BSART=UBZUB
Add-On Table: Inbound Quantity > Purchase Quantity EKPO:MENGE- (Move Type (EKBE:
BWART) = Inbound Quantity for 103, 104 (EKBEWESBS))
NG
Go to 5 errror process
Add-On Table: Inbound Quantity <= Purchase Quantity EKPO:MENGE- (Move Type (EKBE:
BWART) = Inbound Quantity for 103, 104(EKBEWESBS))
OK
Go to 1.5
Add-On table: Binning Quantity (921) is not equal to movement type 105 (EKBE: WESBS)
Actual receiving quantity and inbound quantity (103) then reverse the imbalanced actual
receiving quantity with 106 movement type and inbound quantity with movement type (104)
then system should allow to process binning using movement type (921).
OK
Go to 1.5
1.5
1.5.1 1.5.4
1.5 Inbound Process Execute
If all process from 1.5.1 to 1.5.4 is NOT finished successfully, then return to original state, and end as an error.
1.5.1
FUNC_AREAMM
PROJAS
LOCATG1
BUKRS3894
LEG_SYS3PL
FUN_ID0520102
CONV_OBINB_METHOD
Inbound Processing Method is not maintained in the Parameter Table.
13
Obtain from the parameter table the method of entering the goods movement (Select
Single
Search Condition
Parameter TableBUKRS3894
Parameter TableCONV_OBINB_METHOD
When no records can be obtained from the above search condition, the current record
should not be processed and an error message should be outputted to the error file.
MessageInbound Processing Method is not maintained in the Parameter Table.
CASEEKKOBSART=UBZUB
105 Add-On
Ext. Delivery(LIKP-LIFEX) Reference(MKPF-XBLNR)
CASEEKKOBSART=UB
915
CASEEKKOBSART=ZUB
101
105915101 EKPOELIKZ
X
105915101 MSEGSGTXT2 2
Goods Movement entry

1
FUNC_MOD
If the method of entering the goods movement is FUNC_MOD, the goods movement
should be entered using a function module.
2
BDC
If the method of entering the goods movement is BDC, the goods movememt should be
entered using batch input.
14
-1CIN
-1.1 Chapter-ID J_1IMTCHID
Material and ChapterID

combination for Material&1 Plant&2 does not exist.
-1.2 CENVAT Determination
CENVAT Determination not

maintained for Material:&1 Plant:&2 .
-1CIN Master Check
-1.1 Using the material and the plant from the inbound information , the Material
andChapter-ID combination master needs to be checkedJ_1IMTCHID
If the master does not exist, an error mssage needs to be outputted and the
current record shlould not be prcessed. Error MessageMaterial and
ChapterID combination for Material&1MaterialPlant&2Plant does not
exist.
-1.2 Using the material and the plant from the inbound information, the CENVAT
Determination needs to be checked(J_1IMODDET)
If the master does not exist, an error mssage needs to be outputted and the
current record shlould not be prcessed. Error MessageCENVAT
Determination not maintained for Material:&1Material Plant:&2Plant.
-2
1)A01R01 105
105
2)X
3)MIGO MIGO X
4)MIGO MIGO X
-2Change the default values for the userIf the record does not exist, the record needs
to be added
15
1)If the defautl value for Executable ActionA01Goods Receiptand Reference

DocumentR01Purchase Orderis a value other than 105, the default values
needs to be set to 105 (Action: MIGO_DEFAULTS;Element: A01R01BWART)
2)If the default value for the Display Tips is blank, the Display Tips needs to be set
toX (Action: MIGO_TIPS; Element: HELP_DEFAULTS_CHANGED)
3)If the MIGO header toggle bar visibility is blank, the MIGO header toggle bar
visibility needs to be set to X (Action: MIGO_HEADER_TOGGLER; Element:
VISIBILITY )
4) If the MIGO line toggle bar visibility is blank, the MIGO line toggle bar visibility
needs to be set to X (Action: MIGO_DETAIL_TOGGLER; Element: VISIBILITY)
-3
-3.1
1)
2)Excise InvoiceHeader
3)
4) Tax default informations CVD

Condition Type A/P
5)()
CVD Condition Type A/P
6)()
CVD Condition Type A/P
-3.2
4.6 Functional Map Domestic BDC
-3.3
4.6 Functional Map Overseas BDC
-3Enter Inbound Delivery

-3.1Determine whether the vendor is domestic or overseas
16
1) Using the purchase document number, obtain the Number of the document
condition. (EKKO)
2) Obtain the company information using the company code in the Excise
Invoice Header Internal table (T001)
3) Obtain the tax calculation procedure using the the country code from the
company code information obtained above (T005)
4) Obtain from the CVD Condition Type A/P from the Tax default information
using the tax caulculation procedure obtained from the
above(J_1IEXCDEF)
5) If the CVD Condition Type A/P exists in the Conditions (Transaction Data)
using the Number of the document condition, the procesing purchase order
is considered overseas. (KONV)
6) If the CVD Condition Type A/P does not exists in the Conditions
(Transaction Data) using the Number of the document condition, the
procesing purchase order is considered domestic(KONV)
-3.2When the vendor is a domestic supplier
4.6 View the Functional Map Domestic BDC
Goods movement needs to be entered using function module
-3.3When the vendor is a overseas supplier
4.6 View the Functional Map Overseas BDC
Goods movement needs to be entered using function module
-4
-4Return the defualt values

Return the defualf values of the user to the values before executing the inbound
delivery
BDCFUNC_MOD
Processing Method Invalid (Processing Method1&)

3
If the method of entering the goods movement value is other than BDC or
FUNC_MOD, then process is considered an error, and the curent record is not
processed. Error Message Processing Method Invalid (Processing Method1&method
of entering the goods movement)
17
1.5.1 Inbound Process

Please set to Hold Stock (Blocked Stock), for the following conditions:
CASE For all items except EKKO: BSART=UB, ZUB

Inbound process execution using Move Type 105For the Inbound Process, base on the
inbound delivery number maintained in the Add-On Table, fetch the Ext. Delivery (LIKP-LIFEX), then set
the fetched value to the Reference (MKPF-XBLNR) to execute the inbound process
After completion of delivery instruction (103), system should check, Binning Quantity (921)
with delivery instruction quantity (103) and actual receiving quantity (105) from Add-on table. If there is
any mismatch, System should reverse the actual receiving quantity with movement type 106 and
delivery instruction quantity with movement type 104 .This changes only applicable for NMIPL (company
code 3894) business process.
CASE
EKKO: BSART=UB
Inbound Process execution using Move Type 915
CASE EKKO: BSART=ZUB

Inbound process execution using Move Type 101
In order for the above Move Type 105, 915, 101, set the Delivery completion segment (EKPOELIKZ) Flag to X.
In order for the above Move Type 105, 915, 101, set the system time: 2 digits, munites;
2digits in Inbound deliverys item text(MSEG-SGTXT).
1.5.2
Add-On EKPO:MENGE
EKPO-MENGE
Initial order quantity
1.5.2 Update the order quantity on the purchase order

Add-On Table: Actual Inventory Quantity/Actual Inbound QuantityEKPO:MENGE (Order
Quantity)
Update to the actual inbound quantity using the received data for Order Quantity (EKPOMENGE)
18
Even no change in number of quantity, insert the original order quantity in the item text Initial
order quantity
1.5.3
EKPOLABNR
6 YYYYMMDDYYYYMMDD
1.5.3 Update item status on the Purchase Order
Update status to EKPO: LABNR
Status to 6 YYYYMMDD. YYYYMMDD will be the system date.
1.5.4 Add-On
C
1.5.4 Update the process status on the Add-On Table
Update the status to C for the target process record
2. Add-On
F/#=11
DATA = H30G30K30
Add-On D or C
( EError)
Add-On =
2. Inbound Process: Extract the target data from the Add-On Table (Return Goods order)
Item F/#=11
DATA Segment = H30, G30, K30
2.5
Add-On =VBAKVBELN
Add-On =VBAPPOSNR
19
Add-On No.=
Add-On No.Add-On X
OK
2.2
NG
2.5 Order existence check
Add-On Table: Sales Number=VBAK: VBELN
Add-On Table: Sales Item Number=VBAP: POSNR
Add-On Table: Issue No.=Sales Order:Item Text
Add-On Table: Isse No. Add-On Table: Deletion Flag X

OK
Go to2.2
NG
2.6
Add-On =VBAKVBELN
Add-On =VBAPPOSNR
(VBUK:BUCHKLFGSKC)
OK
2.3
NG
2.6 Inbound Check for corresponding Order number

Add-On Table: Sales Item Number=VBAP: POSNR
When Sales Order Header status is NOT inbounded ( (VBUK: BUCHKLFGSKC))
OK
Go to 2.3
NG
2.7
Add-On =VBAKVBELN
Add-On =VBAPPOSNR
(VBUK: WBSTKC)
VBFA
OK
2.4
NG
2.7 Inbound Order existence check

Add-On table: Sales Number=VBAK: VBELN
Add-On table: Sales Item Number=VBAP: POSNR
20
When Inbound document Header status is NOT inbounded ( (VBUK: WBSTKC))

If Inbound order is existing for the successive order VBFA
OK
Go to 2.
NG
2.8
Add-On
NG
Add-On <=
OK
2.5
2.8 Quantity Chec

Add-On Table: Inbound quantity > Order quantity
NG
Add-On Table: Inbound Quantity <= Order quantity

OK
Go to 2.5
2.9
2.5.1 2.5.2
2.9.4
651
2.9.5
2.4
2.9.6 Add-On
C
2.9 Inbound Process Execution
If all process from 2.5.1 to 2.5.2 is NOT finished successfully, then return to original state, and end as an error
2.9.4 Inbound Process
For Stock Type Hold Stock, process the following inbound process at each move type
Inbound process execution for Move Type 651
2.9.5 Change in order quantity for sales order

When the inbound quantity (at 2.4 quantity check) is less than the order quantity, change the order quantity
to inbound quantity.
21

Update the status to C for the process target record.
3. Add-On
F/#=12
DATA = A11A21U11U21V11N31H31G31K31
( EError)
Add-On =
3. Inventory Process: Extract the target data from the Add-On Table (target all patterns)
Item F/#=12
DATA Segment = A11, A21, U11, U21, V11, N31, H31, G31, K31
3.9
DATA = A11A21U11U21V11N31K31
Add-On =EKKOEBELN
Add-On =EKPOEBELP
Add-On No.=EKPOSGTXT
Add-On No. X
DATA =H31G31
Add-On =VBAKVBELN
Add-On =VBAPPOSNR
Add-On No.=
Add-On No. X
3.9.1 UB
SalesOrder No.TEXTID=15 Add-On Shipping
Instruction Table
OK
3.2
NG
22

DATA Segment: A11, A21, U11, U21, V11, N31, K31
Add-On Table: Sales Number=EKKO: EBELN
Add-On Table: Sales Item Number=EKPO: EBELP
Add-On Table: Issu No.=EKPO: SGTXT
Add-On Table: Issue No.Deletion Flag X
DATA Segment =H31, G31
Add-On Table: Sales Item Number =VBAP: POSNR
Add-On Table: Issue No.=Sales Order: Item Text
3.9.1 When Order Type is UB
Check if Purchase Order Item Text: Sales Order No. (TEXTID=15) exists
in the Add-On Table.

OK
Go to 3.2
NG
3.10 No.
Add-On =EKKOEBELN
Add-On =EKPOEBELP
Add-On =VBAKVBELN
Add-On =VBAPPOSNR
Add-On No. F/#=11 C
EKPOELIKZX
(VBUK: BUCHKLFGSK=C ,VBUK: WBSTK=C)
OK
3.3
NG
3.11 Inbound check for corresponding Issue No.
Add-On Table: Purchase Number=EKKOEBELN
Add-On Table: Purchase Item Number =EKPOEBELP
Add-On Table: Sales Number=VBAKVBELN
Add-On Table: Sales Item Number =VBAPPOSNR
When in the Add-On Table, there exists a same Issue No. with F/#=11, and holds a
status=C.
23
(For Purhcase case) Delivery Completion Segment (EXPO: ELIKZ) = X, in the case for
Sales, Inbound document status as Delivery Complete. ((VBUK: BUCHKLFGSK=C VBUK:

WBSTK=C)
OK
Go to 3.3
NG
3.12
No. Add-On F/#=12 (STATUS=C)
Add-On
NG
Add-On =
OK
3.4

Add-On F/#=12 Add-On
NG
Add-On <= F/#=12 Add-On

OK
3.4

NG
Add-On = F/#=12 Add-On

OK
3.4
]
3.12 Inventory Quantity Check
When there is not exist a same Issue No. in the Add-On Table with the record of F/#=12
(STATUS=C)
Add-On Table: Delivery Instruction Quantity <> (Inventory Quanity + Inventory Remainder
Quantity)
NG
Add-On Table: Delivery Instruction Quantity = (Inventory Quanity + Inventory Remainder

Quantity)
OK
Go to 3.4
When there exists a same Issue No. in the Add-On Table with the record of F/#=12 (STATUS=C)
24
Add-On Table: Inventory Quantity > Previously received F/# = 12 in the Add-On Table: Inventory
Remainder Quantity
NG
Add-On Table: Inventory <= Previously received F/# = 12 in the Add-On Table: Inventory
Remainder Quantity
OK
Go to 3.4
Add-On Table: (Inventory Quantity + Inventory Remainder Quantity) <> Previously received F/# =
12 in the Add-On Table: Inventory Remainder Quantity
NG
Add-On Table: (Inventory Quantity + Inventory Remainder Quantity) = Previously received F/# =
12 in the Add-On Table: Inventory Remainder Quantity
OK
Go to 3.4
Please refer to Inventory Check for more information
3.13
EKPO:LGOBELGORT VBAPLGORT
Add-On Depot
Add-On
NG
Add-On <=
OK
3.5
3.13 Hold Stock Quantity Check

Hold Location EKPO:LGOBE LGORT (Purchase Order) or VBAP: LGORT (Sales Order)
Add-On Table: DepotPlant
Add-On Table: Inventory Quantity > Hold Stock Quantity
NG
Go to 5error process
Add-On Table: Inventory Quantity <= Hold StockQuantity

OK
Go to 3.5
3.14
3.5.1 3.5.4
3.14.1
25

FUNC_AREAMM
PROJAS
LOCATG1
LEG_SYS3PL
FUN_ID0520102
CONV_OBINBOUND
SAP_VAL
Binning Movement Type is not maintained in the Parameter Table.
Obtain from the parameter table the binning goods movement type (Select Single
Search Condition
Parameter TableCONV_OBINBOUND
If no records can be obtained from the above search condition, the current record should
not be processed and an error message should be outputted to the error file. Error
MessageBinning Movement Type is not maintained in the Parameter Table.
Obtain from the parameter table the binning goods movement type (Select Single
Search Condition
Parameter TableBUKRS3894
Parameter TableCONV_OBCOMPCODE
Parameter Table SAP_VAL = LOCAL
26
When no records can be obtained from the above search condition, the current record
should not be processed and an error message should be outputted to the error file.
If the value matched with the parameter table then system should check binning quantity
(921) with actual receiving quantity (105) and delivery instruction quantity (103).
343
No.
3.14 Inventory Process Execution

3.14.1 Inventory Process
Inventory Process Execution (Stock Transfer) forMoveType 343, use the movement type
obtained from above
Maintain the process target Issue No. in the Goods Order Item Text
3.14.2
EKPOLABNR
7 YYYYMMDDYYYYMMDD
3.14.2 Update Process Status (for purchase order only)
When, Inventory Remainder Quantity = 0, Update the Status to EKPO: LABNR
Status to 7YYYYMMDD, YYYYMMDD will be the system date.
3.14.3 UB Add-On ShippingInstruction
Add-On ShippingInstruction Sales Order
No. 1
No. 2
Add-On ShippingInstruction DATA U30orU40U30U40
(ALCQUN BNQUN)
27
3.14.3 When Purchase Order Type = UB, then update the Inventory Quantity in the Add-On Table
(Shipping Instruction)
Sales Order Number from the Add-On Table: Shipping Instruction = 1 st row of the item text from
the Sales order (Sales Order No.)
Item Number from the Add-On Table: Shipping Instruction = 2 nd row of the item text from the
Sales order (Sales Order No.)
Add-On Table: Shipping Instruction Data Segment = U30 or U40 (maintain U30, U40 in the
parameter table)
Update the quantity in the field Inventory Quantity (ALCQUN BNQUN) when the above
condition matches. Updating method is to update the total of the addition of the existing quantity in
the field with the new quantity for the field.
3.14.4 Add-On
C
Update status to C for the process target record
3.15 ()
No. Add-On F/#=12 1
122
3.15 Return Inbound Execution (Not Used)

If the same Issue No with Add-On Table: F/#=12 record does not exist when processing the
Existence Process Target record (i.e. when there is only 1 record), execute the Inbound Cancel (Move
Type 122: Return Goods) for the quantity of {Delivery Instruction Quantity (Inventory Quanity +
Inventory Remainder Quantity)}, then change the inbound quantity to the actual inbound quantity.
4. Add-On
F/#=12
DATA = A12A22U12U22V12N32H32G32K32
( EError)
Add-On =
4. Defect Goods Process: Extract the Target Data in the Add-On Table (All patterns will be the target)
28

Item F/#=12
DATA Segment = A12A22U12U22V12N32H32G32K32
4.15
DATA = A12A22U12U22V12N32K32
Add-On =EKKOBSART
Add-On =EKPOEBELP
Add-On No.=EKPOSGTXT
Add-On No. X
DATA =H32G32
Add-On =VBAKVBELN
Add-On =VBAPPOSNR
Add-On No.=
Add-On No. X
OK
4.2
NG

DATA Segment = A12, A22, U12, U22, V12, N32, K32
Add-On Table: Purchase Number=EKKOBSART
Add-On Table: Purchase Item Number=EKPOEBELP
Add-On Table: Issue No.=EKPOSGTXT
DATA Segment =H32, G32
Add-On Table: Sales Number=VBAKVBELN
Add-On Table: Issue No.=Sales OrderItem Text

OK
Go to 4.2
NG
4.16 No.
29
Add-On =EKKOBSART
Add-On =EKPOEBELP
Add-On =VBAKVBELN
Add-On =VBAPPOSNR
Add-On No. F/#=11 C
EKPOELIKZX
((VBUK: BUCHKLFGSK=C VBUK: WBSTK=C)
OK
4.3
NG
4.16 Inbound Check for corresponding Issue No
Add-On Table: Purchase Number =EKKOBSART
Add-On Table: Purchase Item Number =EKPOEBELP
Add-On Table:Sales Number =VBAKVBELN
When there exists a same Issue No of F/#=11with status=C in the Add-On Table
(For Purhcase case) Delivery Completion Segment (EXPO: ELIKZ) = X, in the case for
Sales, Inbound document status as Delivery Complete. ((VBUK: BUCHKLFGSK=C VBUK:

WBSTK=C)
OK
Go to 4.3
NG
4.17
Add-On
NG
Add-On =
OK
4.4

NG
Add-On <= F/#=12 Add-On

OK
4.4
30
NG
Add-On = F/#=12 Add-On
OK
4.4
4.17 Invenroty Quantity Check

When there is not exist a same Issue No. in the Add-On Table with the record of F/#=12
(STATUS=C)
Add-On Table: Delivery Instruction Quantity <> (DefectGoods Quantity + Inventory Remainder
Quantity)
NG
Add-On Table: Delivery Instruction Quantity = (DefectGoods Quantity + Inventory Remainder

Quantity)
OK
Go to 4.4
When there exists a same Issue No. in the Add-On Table with the record of F/#=12 (STATUS=C)
Add-On Table: DefectGoods Quantity > Previously received F/# = 12 in the Add-On Table:
Inventory Remainder Quantity
NG
Add-On Table: DefectGoods Quantity <= Previously received F/# = 12 in the Add-On Table:
Inventory Remainder Quantity
OK
Go to 4.4
Add-On Table: (DefectGoods Quantity + Inventory Remainder Quantity) <> Previously received
F/# = 12 in the Add-On Table: Inventory Remainder Quantity
NG
Add-On Table: (DefectGoods Quantity + Inventory Remainder Quantity) = Previously received

F/# = 12 in the Add-On Table: Inventory Remainder Quantity
OK
Go to 4.4
Please refer to Inventory Check for more information
4.17
EKPO:LGOBE VBAPLGORT
Add-On Depot
31
Add-On
NG
Add-On <=
OK
4.5
4.18 Hold Stock Quantity Check

Hold Location EKPO:LGOBE (Purchase Order) or VBAP: LGORT (Sales Order)
Add-On Table: DepotPlant
Add-On Table: Defect Goods Quantity > Hold Stock Quantity
NG
Add-On Table: Defect Goods Quantity <= Hold StockQuantity

OK
Go to 4.5
4.19
4.5.1 4.5.4
4.19.1
909
No.
19.20 Defect Goods Execution

4.19.1 Defect Goods Process
Hold Location Move Process Execute for Move Type 909 (Move the Stock Status by Hold
Stock)
Maintain the process target Issue No. in the Goods Order Item Text
4.19.2
EKPOLABNR
7 YYYYMMDDYYYYMMDD
4.19.3 UB Add-On ShippingInstruction
No. 1
No. 2
32
Add-On ShippingInstruction DATA U30orU40U30U40
(BNQUN)
4.19When Purchase Order Type = UB, then update the Inventory Quantity in the Add-On Table (Shipping
Instruction)
Sales Order Number from the Add-On Table: Shipping Instruction = 1 st row of the item text from
the Sales order (Sales Order No.)
Item Number from the Add-On Table: Shipping Instruction = 2 nd row of the item text from the
Sales order (Sales Order No.)
Add-On Table: Shipping Instruction Data Segment = U30 or U40 (maintain U30, U40 in the
parameter table)
Update the quantity in the field Inventory Quantity (BNQUN) when the above condition matches.
Updating method is to update the total of the addition of the existing quantity in the field with the
new quantity for the field
4.19.4 Add-On
C
20.20 Defect Goods Execution
4.19.2 Defect Goods Process
Hold Location Move Process Execute for Move Type 909 (Move the Stock Status by Hold
Stock)
Maintain the transferred Store Location per Plant in the parameter table.
4.19.3 Update the process status (for Purchase only)

For Inventory Remainder Quantity 0, then update the status to EKPO: LABNR
Status to 7 YYYYMMDD, YYYYMMDD system date
Update the status to C for the process target record
33
4.20 ()
No. Add-On F/#=12 1
122
20.21 Return Inbound Execution (Not Used)

If the same Issue No with Add-On Table: F/#=12 record does not exist when processing the
Existence Process Target record (i.e. when there is only 1 record), execute the Inbound Cancel (Move
Type 122: Return Goods) for the quantity of {Delivery Instruction Quantity (Defect Goods + Inventory
Remainder Quantity)}, then change the inbound quantity to the actual inbound quantity.
5.
20.21
5.21.1
VOFM
Include RV50C601
5.21.2
5.21.2.1
ZASG1XXT002
ZASG1XXT002-FUNC_AREA=MM
ZASG1XXT002-PROJ=AS
ZASG1XXT002-LOCAT=G1
ZASG1XXT002-BURKS=VBAK-BURKS_VF
ZASG1XXT002-FUN_ID=0520102
ZASG1XXT002-FLD1=VKORG
ZASG1XXT002-FLD2=VTWEG
ZASG1XXT002-FLD3=VSTEL
ZASG1XXT002-SAP_V1=VBAK-VKORG
ZASG1XXT002-SAP_V2=VBAK-VTWEG
ZASG1XXT002-SAP_V3=VBAP-VSTEL
5.21.2.2
LIKP-ZUKRLCVBAP-VBELN
CVBAP-POSNR
34
5. Creation of Return Delivery Document by Item

20.21 Create Return Delivery Header by Sales Order Item
5.21.1 Create a new Routine
From t-code VOFM, in Menu: Data transfer / Deliveries, copy standard Routine 1 (Header) to 601
(Include RV50C601).
5.21.2 Development of the Routine
5.21.2.1 Execution of the Changed / Added logic for relevant Organizations
Control that the logic that needs to be changed / added in comparison with the standard routine will
be processed while creating delivery documents only for corresponding sales orders that match
with the following conditions stored in the parameter table ZASG1XXT002:
ZASG1XXT002-FUNC_AREA=MM
ZASG1XXT002-PROJ=AS
ZASG1XXT002-LOCAT=G1
ZASG1XXT002-BURKS=VBAK-BURKS_VF
ZASG1XXT002-FUN_ID=0520102
ZASG1XXT002-FLD1=VKORG
ZASG1XXT002-FLD2=VTWEG
ZASG1XXT002-FLD3=VSTEL
ZASG1XXT002-SAP_V2=VBAK-VKORG
ZASG1XXT002-SAP_V2=VBAK-VTWEG
ZASG1XXT002-SAP_V3=VBAP-VSTEL
5.21.2.2 Contents of the changed / added logic

Set the combination criteria of the delivery header (LIKP-ZUKRL) with the concatenation of the
corresponding sales document number (CVBAP-VBELN) and sales document item number
(CVBAP-POSNR)
6. Job Log/Warning/Error Level
6.1 Warning File
6.1.1 4.6 Functional Data Map Mapping Sheet Description Warning Check
Field
6. Determining Job Log/Warning/Error Level
6.1 Warning File Output
6.1.1 The target field is when there is a documentation as Warning Check in the Description of
Mapping Sheet from the 4.6 Functional Data Map
35
6.2 Error File

6.2.1 4 Error Error File
6.2.2 Error Error File
6.2.2.1 Add-On Error
Time Stamp
Process Name
Program ID
Key Information
Error InformationError CodeError Description
6.2 Error File output

6.2.1 If a error occurs from 1 4 process, then create a Error File
6.2.2 Out put the Error File with Error Information
6.2.2.1 If the error occurs when inserting to the Add-On Table, then output the following
Time Stamp
Process Name
Program ID
Key Information: Order Number, Item Number
Error InformationError CodeError Description
6.3 Job Log

6.3.1 15 Job Log
6.3.1.1 Add-On Error
6.3 Job Log Output
6.3.1 If the process from 1 5 successfully completes, then output to JobLog
6.3.1.1 Output the Total Count, Successful Count, Error Count for the insert to the Add-On Table
6.4 Information File
6.4.1
No
Time Stamp
Process Name
Program ID
Key Information(EKKO:LIFNR)DATA
36
(Zero)
(Zero)
Information
Error Error CodeError Description
6.4 Information File Output

6.4.1 Output a file for each records process result (Sort the output order by Issue No. If Issue No.
includes Error data, remove the target Issue No. data (including Complete data) to the top.)
Time Stamp
Process Name
Program ID
Key Information: Supplier code(EKKO:LIFNR), Parts Number, Issue No, Data Segment,
(Purchase Number, Item Number, or Sales Number, Item Number), Inbound Number, Parts
Number, Delivery Instruction Quantity, Actual Inbound Quantity, Inventory Remainder Quantity
(Before), Actual Inventory Quantity, Defect Goods Quantity, Inventory Remainder Quantity
(After), Inventory Remainder Quantity(Calculation), Difference Quantity, Goods Order Number,
Status (Procurement process status)
Delivery Instruction Quantity : Inbound Process : Delivery Instruction Quantity

Other
Actual Inbound Quantity : Inbound Process : Actual Inbound Quantity

Other
: - (Zero)
: Delivery Instruction Quantity
Inventory Remainder Quantity (Before) : first data; Delivery Instruction Quantity, other;
Previously received Inventory Remainder Quantity
37
Actual Inventory Quantity : Inbound Process : - (Zero)

Other
: Actual Inbound Quantity
Defect Goods Quantity : Defect Goods Quantity
Inventory Remainder Quantity (After) : Inventory Remainder Quantity
Inventory Remainder Quantity(Calculation) : Inventory Remainder Quantity (Before)

(Actual Inventory Quantity + Defect Goods Quantity)
Difference Quantity : Inventory Remainder Quantity (After) - Inventory Remainder

Quantity(Calculation)
Information
When finished successful: Goods Order number
When finished Error: Error Code, Error Description
When the quantity is revised b/c the inbound quantity differs for Sales Order and Purchase
Order: Output the quantity for the change before & after.
7. Add-On
Complete: C
Error:E
7. Status Update Process for Inbound Preparation Information (Add-On Table)

Update each process status to each record according to the following
Complete: C
Error:E
7.
7.1
8. Completion Process
8.1 All process is complete
38
2.8
Process Flow
3PL
Error
File
Error
File
PO
Line
(EKPO)
MM-05-201-01
Send
MM-05-201-02
I/F Inbound
PO
Information
Material
Master
(MARA)
Material
Master
(MARC)
PO
Line
(EKPO)
Delivery
Line
LIPS
Add-On
Table
Sales
Document
Header
VBAK
Sales
Document
Line
VBAP
Document
Segment
: Material
(MSEG)
Conversion
Master
Parameter Table
Master
Combination of
Modvat Determination
Material Number
Table ( Input Material
and Chapter ID
->Output Material)
39
Shipping
Instruction
(Add-On
Table)
2.9
Systems Referred To
N/A
2.10 Processing Options

Processing Mode:
( X ) Batch
Frequency:
( ) Annually ( ) Quarterly
( X ) Daily
( ) Online
( ) Monthly
( ) Weekly
( ) Other:
Lifetime of
( X) Permanent
development
( ) Temporary, e.g. until rollouts are complete, specify details
2.11 Security Requirements

Job Job
Error
In order to execute job, job user will have authority.
In order to have error recovery, system maintenance person will have authority.
40
Interface/Conversion Information
3.1
Integration Point Overview
Add-On
For this function, extract the Planned Shipping Information from Shipping Order, Purchase Order in the SAP,
then insert to the Add-on Table. Also, the target period corresponds to either the next 1 week worth of plan
shipment and next day plan shipment.
3.2
Summary
For interface/conversion only:

Name of Interface or
Conversion:
Mapping Attachment:
( ) No
( X ) Yes
Sample Data
( X ) No
Attachment:
( ) Yes - Filename:
For Conversions:
() Master Data
3.3
(X) Transactional Data
Dependencies/Prerequisites
Executing parameter are set in the executing screen, and the parameter value master and conversion master hasa
value set.
41
3.4
Interface Information
Describe the interface by specifying the following:

Direction of Interface:
() Inbound
(X ) Outbound
( ) Both (Description of return interface)

Frequency:
( ) Real-time ( X ) Batch
( ) Other
Processing
( X ) Sequential
( ) Parallel allowed
Filters:
Filtering Requirements
N/A
Triggers:
Transaction Name or Batch Job:
Batch Job
Service Levels / System Availability
N/A
Other Processing Requirement: (not required for all interfaces):

Application Post Processing:
Close Loop Processing:
N/A
Routing Rules:
N/A
3.5
Legacy/External Systems Involved
Interface File Layout
42
Interface File/Message Format (NON-R/3 SAP System)

Relevant Tables
Input File:
File Name:
Layout
3.6
Functional Data Map
Add- On
3.7
Domestic BDC
Overseas BDC
Selection Screen (if applicable)
Field Title/Screen
Label
Type
Size
Manda
tory
Wild
Cards
?
Range
Required?
Reference
Field Name
Criteria
Validation
3.8
Company Code
Plant
Procurement
process status
Error File Path
60
Error File Name
128
Information File
Path
60
Information File
Name
128
Process Date
xception Handling Rules

N/A
3.9
Impact on Legacy Systems
N/A
43
3.10 SAP Transaction (Interface that create data in SAP)

N/A
44
3.11 Reference Tables

Table Name
SAP Standard
Add-On Table
Table
EKPO (Purchasing
Document Item)
LIPS (Delivery
Item)
MARA(Material
Master)
MARC(Material
Master)
VBAK(Sales
Document Header)
VBAP(Sales
Document Item)
MSEG(Document
Segment: Material)
V
Parameter Table
Conversion Value
Master
ShippingInstruction
J_1IMTCHID
V
V
(Combination of
Material Number and
Chapter ID)
45
J_1IMODDET(Modva
t Determination
Table (Input Material>Output Material))
3.12 Additional Information
N/A
46
Revision History
Revision History
Version
Revision Date
Summary of Changes
Updated By
101
2009/10/19
New Document
Kazuya Sakamoto
200
2009/11/20
Revised
Kazuya Sakamoto
201
2009/11/25
For QA
Kazuya Sakamoto
202
2009/11/30
For Shipping Instruction Table
Kazuya Sakamoto
203
2009/12/9
For Issue List( Changed input file pattern
Kazuya Sakamoto
K30.
204
2009/12/10
Add-On table status not eaual C or D
Kazuya Sakamoto
condition add.
205
2009/12/14
Add the Order status
Kazuya Sakamoto
Change the 1.5.1 section.

206
2009/12/16
BUCHKLFGSK
Kazuya Sakamoto
207
2009//12/18
Add destination Store Loc, to parameter table.
Kazuya Sakamoto
208
2009/12/19
Add EKPO-ELIKZ logic
Kazuya Sakamoto
209
2009/12/21
P.18ALCQUN BNQUN
Kazuya Sakamoto
Change search key Salesorder to Inbound Doc

for VBUK
P.22
Add the logic that update Add-On table Qty
210
2009/12/23
P.21
Kazuya Sakamoto
Inventory QuantityDGQuantity
211
2010/1/5
P.18P.22
Kazuya Sakamoto
Add the update condition of

Shippinginstruction table.
212
2010/1/21
P.10
Kazuya Sakamoto
Add the referenceNo. when post.

213
2010/1/26
P.22
Kazuya Sakamoto
Maintain the process target Issue No. in

the Goods Order Item Text
214
2010/2/5
P.9P.10
Kazuya Sakamoto
Add for receiveing info program.
47
215
2010/2/9
P.31
Kazuya Sakamoto
Information File Output PATH

216
2010/4/8
Delete F#=13
Kazuya Sakamoto
Add reference document

217
2010/6/4
P.8.12.14.15. 20
Hiroshi Murakami
Change Extract Add-on table

P. 16. 17. 22. 23
Change Invenroty Quantity Check
P. 26. 27.28
Change Information File Output / Sort the
output order
P. 33
Add Selection Screen Field: Procurement
process status
218
2010/6/11
Exit Addition
Akira Sakabe
Inbound process change (Batch Input)

Binning (Inventory) movement type change
219
2010/7/21
Enhancement Addition
Akira Sakabe
Batch Input Removal

220
2010/8/2
Add Routine 601 for creating deliveries by
Ken Ggout
sales order item

221
2010/12/23
Change incorporated to hand the shortages
Thanuskodi
inbound quantity.
Thangasamy
P.5
2.1Overview Updates
P.6
2.6 Dependencies Updates
P.13
1.4 Quantity Check Changes Updates
P.17
1.5.1. Inbound Process Updates
P.26
48
3.14.1
49

FS NMIPL MM-05-201-02 Ver221.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FS NMIPL MM-05-201-02 Ver221.0

Uploaded by

Copyright:

Available Formats

NMIPL After Sales Parts System Project

Inbound Inventory Information Receive

Inbound Inventory Information Receive

All Rights Reserved, Copyright NISSAN MOTORS CO., LTD.

Document Preparation and Approval Page

Nissan Biz (EAS)

Nissan Biz (R40)

All Rights Reserved, Copyright NISSAN MOTORS CO., LTD.

Purpose of the Document............................................................................................... 4

Change Management Considerations/Users and Volumes..............................................6

Systems Referred To..................................................................................................... 40

2.10 Processing Options....................................................................................................... 40

Integration Point Overview........................................................................................... 41

Legacy/External Systems Involved................................................................................42

Functional Data Map..................................................................................................... 43

Selection Screen (if applicable).....................................................................................43

Exception Handling Rules............................................................................................. 43

Impact on Legacy Systems........................................................................................... 43

3.10 SAP Transaction (Interface that create data in SAP)......................................................43

All Rights Reserved, Copyright NISSAN MOTORS CO., LTD.

Purpose of the Document

Interface/ Conversion Information (Section 4)

All Rights Reserved, Copyright NISSAN MOTORS CO., LTD.

2.1.3 Data Scope

2.1.4 Generate Format

All Rights Reserved, Copyright NISSAN MOTORS CO., LTD.

( ) Tax Software ( ) CRM

Change Management Considerations/Users and Volumes

2.4.1 Change Management Considerations

All Rights Reserved, Copyright NISSAN MOTORS CO., LTD.

All Rights Reserved, Copyright NISSAN MOTORS CO., LTD.

0.1 MIGO EXIT

2 Excise Action 01(Capture & Post Excise Invoice) 05(Part 1)

All Rights Reserved, Copyright NISSAN MOTORS CO., LTD.

Incoming Excise Invoice CAPIND() ORIG_CAPIND()(

Goods Movement Header Change condition

All Rights Reserved, Copyright NISSAN MOTORS CO., LTD.

Condition 3 When the goods movement transaction type is not Others

Goods movememt screen refresh

The following process needs to be executed

All Rights Reserved, Copyright NISSAN MOTORS CO., LTD.

1.1 Order Existence Check

Add-On Table: Purchase Number=EKKO: EBELN

Add-On Table: Purchase Item Number=EKPO: EBELP

Add-On Table: Issue No.=EKPO: BEDNR

Add-On Table: Issue No.Add-On Table: Deletion Flag: X

All Rights Reserved, Copyright NISSAN MOTORS CO., LTD.

1.2 Inbound Check for corresponding Order Number

1.3 Existence Check for Inbound Order

All Rights Reserved, Copyright NISSAN MOTORS CO., LTD.

Add-On <= EKPO:MENGE-EKBE

1.4 Quantity Check

Inbound Processing Method is not maintained in the Parameter Table.

All Rights Reserved, Copyright NISSAN MOTORS CO., LTD.

Goods Movement entry

All Rights Reserved, Copyright NISSAN MOTORS CO., LTD.

Material and ChapterID

CENVAT Determination not

All Rights Reserved, Copyright NISSAN MOTORS CO., LTD.

1)If the defautl value for Executable ActionA01Goods Receiptand Reference

4) Tax default informations CVD

-3Enter Inbound Delivery

All Rights Reserved, Copyright NISSAN MOTORS CO., LTD.