Technical specification : SD(Logistics)_Order_Processing

Technical Specification
Report
Date 18-Nov-10
Description Report to display overall order status related to delivery, Shipment and
Billing
Prepared by
(Technical Person)
Ravin Joshi
OBJECT OVERVIEW
Technical Name ZOrder_Process
Description
Sales Report for Overall Order Status related to delivery, Shipment and
Billing
Development Package
ZSDLOGIS
Message Class
ZORDER_MSG
Program Type
Executable Program
Module
Sales and Distribution (SD- Logistics)
Page 1 of 12
9/23/2013 7:09:09 a9/p9
technicalspecificationlogisticsworkqueuefororderprocessing-130923020907-phpapp02.doc

TECHNICAL SPECIFICATION
DOCUMENT VERSION HISTORY
Version
No
Date
Revised Author Summary of Changes
1.0
11/18/201
0
Ravin Joshi Initial Draft
1.1
11/24/201
1
Ravin Joshi Changes
1.2
11/30/201
0
Ravin Joshi Changes
1.3
12/13/201
0
Ravin Joshi Changes
Document Version History
APPROVAL TRACKING
Role Approver Date
Author Ravin Joshi 11/18/2010
Peer Reviewer
Business Process eXpert (BPX)
Business Process Architect (BPA)
Solution Architect
Page 2 of 12
9/23/2013 7:09:09 a9/p9

DEPENDENCIES/CONSTRAINT
None identified at this time
ASSUMPTIONS
- Security not necessary to display information on the summary section
- Security required if display document details is requested
PROCESS DESCRIPTION
Page 3 of 12
9/23/2013 7:09:09 a9/p9

ZOrder_Process is an executable ALV report which consists of following during execution:
- Selection Criteria
- Order Processor Queue
- Sales Oder Summary
- Billing Summary
Based on Selection Criteria, Order Processor Queue will display:
1) Document Type
2) Sold-To-No
3) Sold-To-Name
4) Ship-To-No
5) Ship-To-Name
6) Shipping Condition
7) Overall Block Status
8) Sales Order No
9) Purchase Order No
10) Delivery Doc
11) Shipping Doc
12) Billing Doc
While clicking on Sales Order No from Order Processor Queue, Sales Order Summary will display:
1. Sales Order No
2. Plant
3. Item
4. Material
5. Material Description
6. Required Delivery Date
7. Confirmed Delivery Date
8. Credit Status
9. Block Status
10. Overall Status
While clicking on Billing Doc from Order Processor Queue, Billing Summary will display:
1) Invoice No.
2) Payor
3) Item
4) Material
5) Material Description
6) Net Value
7) Sales Unit
8) Billing Date
Technical Details: (Covers all fields of Primary List & both Secondary Lists)
Page 4 of 12
9/23/2013 7:09:09 a9/p9

No. Field Name
Table
Name
Technical Field
Name Mandatory Value
1 Document Type VBAK AUART
2 Sold-To-No VBAK KUNNR Y
3 Sold-To-Name KNA1 NAME1
4 Ship-To-No VBAK KUNNR Y
5 Ship-To-Name KNA1 NAME1
6 Shipping Condition VBAK VSBED
7 Overall Block Status VBUK SPSTG
8 Sales Order No VBAK VBELN
9 Purchase Order No
10 Invoice Doc VBFA VBTYP_N J
11 Shipping Doc VBFA VBTYP_N 8
12 Billing Doc VBFA VBTYP_N M
13 Plant VBAP WERKS
14 Material VBAK MATNR
15 Material Description MAKT MKTXT
16 Required Delivery Date VBEP EDATU Y
17 Confirmed Delivery Date VBEP EDATU
18 Credit Status
19 Block Status VBUP LSSTA
20 Overall Status VBUK CMGST
21 Invoice No. VBRP VBELN
22 Payor VBRK KUNRG
23 Item VBRP POSNR
24 Material VBRP MATNR
25 Material Description MAKT MKTXT
26 Net Value VBRP NETWR
27 Sales Unit VBRP VRKME
28 Billing Date VBRK FKDAT
Page 5 of 12
9/23/2013 7:09:10 a9/p9

Flow Chart:
Page 6 of 12
9/23/2013 7:09:10 a9/p9

REPORT TOOL
Report Painter Y Report Writer SAP Query
ABAP program Info system Y ALV
R/3 BW Crystal Reports
PROGRAM NAME LOGIC DIAGRAM AND PSEUDO CODE
ZORDER_PROCESS Report logic mainly covers :
• Fetching data from the selection-screen provided by
user inputs.
Selection Criteria covers :
o Sold-to Party / Ship-to-Party (Mandatory)
o Sales Organization
o Distribution Channel
o Sales Order No.
o Sales Order Type
o Required Delivery Date(Mandatory)
o Material
o Order Status
• Processing data which covers the use of certain select
statements from different tables while checking the
required conditions and based on the inputs provided
from the user.
• Displaying data in the ALV format which covers
interaction functionality by user commands which covers
use of standard function module
‘REUSE_ALV_GRID_DISPLAY’ while building the layout
and fieldcatalog for the same.
• While Displaying data into ALV, the output covers one
basic list: Sales Order Processor Queue & other two
secondary lists: Sales Order Summary and Billing
Summary.
• Sales Order Processor Queue will display:
- DocType
- Sold-to No
- Sold-to Name
- Ship-to No
- Ship-to Name
- Customer PO
- Shipping Cond
- Overall Block Status
- Sales Order No
- Delivery Doc No
- Shipment Doc No
Page 7 of 12
9/23/2013 7:09:09 a9/p9

- Billing Doc No
While Sales Order Summary will display:
- Sales OrderNo
- Plant
- Item
- Material
- Material Desc
- Confirm Delivery Date
- Block Status
- Overall Status
And Billing Summary will display:
- Invoice No
- Payor
- Item
- Material
- Material Desc
- Net Value
- Sales Unit
- Billing Date
Pseudo Code : (Sample for reference only)
*Tables Declaration
Tables: VBAK, VBEP, VBAP, VBUK, VBUP, KNA1, VBKD,
MAKT, VBFA, VBRP, VBRK.
TYPE-POOLS: SLIS.
*Work-Area Declaration
Data : Begin of WA_INPUT, " Input from user
AUART type VBAK-AUART,
KUNNR type VBAK-KUNNR,
VKORG type VBAK-VKORG,
VTWEG type VBAK-VTWEG,
VBELN type VBAK-VBELN,
EDATU type VBEP-EDATU,
MATNR type VBAP-MATNR,
LFSTK type VBUK-LFSTK,
POSNR type VBUP-POSNR,
LSSTA type VBUP-LSSTA,
End of WA_INPUT,
Begin of WA_OUTPUT, "Order Process Queue
AUART type VBAK-AUART,
KUNNR type VBAK-KUNNR,
NAME1 type kna1-name1,
BSTKD type VBKD-BSTKD,
VSBED type VBAK-VSBED,
SPSTG type VBUK-SPSTG,
VBELN type VBAP-VBELN,
D_doc type VBAP-VBELN,
S_doc type VBAP-VBELN,
Page 8 of 12
9/23/2013 7:09:09 a9/p9

B_doc type VBAP-VBELN,
POSNR type VBAP-POSNR,
VBELV type VBFA-VBELV,
POSNV type VBFA-POSNV,
VBTYP_N type VBFA-VBTYP_N,
End of WA_OUTPUT,
*Internal Table & Work-areas
Data : lt_vbap like TABLE OF wa_vbap,
lt_vbfa LIKE TABLE OF wa_vbfa,
lt_vbup LIKE TABLE OF wa_vbup,
lt_vbak LIKE TABLE OF wa_vbak,
lt_vbkd LIKE TABLE OF wa_vbkd,
lt_kna1 LIKE TABLE OF wa_kna1,
lt_vbuk LIKE TABLE OF wa_vbuk,
lt_vbrp LIKE TABLE OF wa_vbrp,
lt_vbrk LIKE TABLE OF wa_vbrk,
lt_makt LIKE TABLE OF wa_makt,
lt_vbep LIKE TABLE OF wa_vbep,
lt_input like TABLE OF WA_INPUT,
lt_output like TABLE OF WA_OUTPUT,
lt_output2 like TABLE OF WA_OUTPUT2,
lt_output3 LIKE TABLE OF WA_OUTPUT3,
wa_fieldcat type slis_fieldcat_alv,
wa_fieldcat2 type slis_fieldcat_alv,
wa_fieldcat3 type slis_fieldcat_alv,
alv_fieldcat TYPE slis_t_fieldcat_alv
,
alv_fieldcat2 TYPE slis_t_fieldcat_al
v,
alv_fieldcat3 TYPE slis_t_fieldcat_al
v,
alv_layout type slis_layout_alv,
alv_layout2 type slis_layout_alv,
alv_layout3 type slis_layout_alv.
*Selection Screen
SELECT-OPTIONS Soldto FOR VBAK-KUNNR.
SELECTION-SCREEN SKIP 1.
*AT Selection Screen
AT SELECTION-SCREEN.
PERFORM Validate_data_Soldto.
*INITIALIZATION
*START-OF-SELECTION.
START-OF-SELECTION.
PERFORM GET_DATA.
PERFORM PROCESS_DATA.
*END-OF-SELECTION.
PERFORM Fieldcat_init.
PERFORM UPDATE_DATA.
alv_layout-colwidth_optimize = 'X'.
alv_layout-zebra = 'X'.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
I_CALLBACK_PROGRAM = 'ZORDER_PROCES
S'
Page 9 of 12
9/23/2013 7:09:09 a9/p9

I_CALLBACK_USER_COMMAND = 'USER_COMMA
ND'
I_GRID_TITLE = 'Sales Order Processing Que
ue'
IS_LAYOUT = alv_layout
IT_FIELDCAT = alv_fieldcat
TABLES
T_OUTTAB = lt_output
IF SY-SUBRC <> 0.
* MESSAGE
ENDIF.
FORM user_command USING ucomm TYPE sy-ucomm
rs_selfield TYPE slis_selfield.
IF rs_selfield-fieldname = 'VBELN'.
*Necessary Action
ELSEIF rs_selfield-fieldname = 'B_doc'.
*Necessary Action
ENDIF.
ENDFORM.
*FORMS :
FORM PROCESS_DATA .
Select KUNNR name1 from kna1 into table lt_k
na1 FOR ALL ENTRIES IN lt_input
where kna1~KUNNR = lt_INPUT-KUNNR.
Select VBELN POSNR BSTKD from VBKD into ta
ble lt_vbkd FOR ALL ENTRIES IN lt_input
where VBKD~VBELN = lt_INPUT-VBELN an
d
VBKD~POSNR = VBUP-POSNR.
Loop at lt_input into WA_input.
WA_OUTPUT-AUART = WA_input-AUART.
:
:
ENDLOOP.
ENDFORM.
FORM GET_DATA .
SELECT
VBAK~AUART
VBAK~KUNNR
VBAK~VKORG
VBAK~VTWEG
VBAK~VBELN
VBEP~EDATU
VBAP~MATNR
VBUK~LFSTK
VBUP~POSNR
VBUP~LSSTA
FROM VBAK INNER JOIN VBUK ON VBAK~VBELN =
VBUK~VBELN
INNER JOIN VBUP ON VBAK~VBELN =
Page 10 of 12
9/23/2013 7:09:09 a9/p9

VBUP~VBELN
INNER JOIN VBAP ON VBUK~VBELN =
VBAP~VBELN
INNER JOIN VBEP ON VBUK~VBELN =
VBEP~VBELN
INTO corresponding fields of TABLE lt_inpu
t
WHERE VBAK~AUART IN Salordty AND
VBAK~KUNNR IN Soldto AND
VBAK~KUNNR IN Shipto AND
VBAK~VKORG IN Salesorg AND
VBAK~VTWEG IN Distchn AND
VBAK~VBELN IN Salordno AND
VBEP~EDATU IN Reqdeldt AND
VBAP~MATNR IN Matrl AND
VBUK~LFSTK IN OrdSta.
ENDFORM. " GET_DATA
FORM FIELDCAT_INIT .
clear wa_fieldcat.
wa_fieldcat-col_pos = 1.
wa_fieldcat-fieldname = 'AUART'.
wa_fieldcat-seltext_m = 'DocType'.
append wa_fieldcat to alv_fieldcat.
clear wa_fieldcat.
:
:
ENDFORM.
FORM PROCESS_ORDER_SUMMARY .
SELECT MATNR MAKTX from MAKT into table lt_m
akt FOR ALL ENTRIES IN lt_input
where MAKT~MATNR = lt_input-matnr and MA
KT~SPRAS = sy-langu.
:
WA_OUTPUT2-VBELN = wa_output-VBELN.
:
APPEND WA_OUTPUT2 to lt_output2.
CLEAR WA_OUTPUT2.
ENDFORM. " PROCESS_ORDER_SUMMARY
:
:
:
END
TECHNICAL ERROR HANDLING
Page 11 of 12
9/23/2013 7:09:09 a9/p9

For error handling purpose, custom message class: ZORDER_MSG has been created which covers all
error messages with different message ids.
For Example,
(1) if the user enters data in selection screen without entering mandatory field: Ship-to/Sold-to entry in
selection field then following error message going to be displayed:
Ship-to/Sold-to required to process request.Plz Select Ship-to/Sold-to.
(2) If the user enters data in Ship-to/Sold-to which do not match other corresponding entry in DDIC itself
while entering other selection criteria then following error message going to be displayed:
No Data found for Ship-to/Sold-to.
(3) If after entering all the selection criteria in to selection screen, no entry found in DDIC itself then
following error message going to be displayed:
No Data Found for selection criteria
Page 12 of 12
9/23/2013 7:09:09 a9/p9

Technical specification : SD(Logistics)_Order_Processing

Recommended

More Related Content

What's hot (20)

Viewers also liked (18)

Similar to Technical specification : SD(Logistics)_Order_Processing (20)

Recently uploaded (20)

Technical specification : SD(Logistics)_Order_Processing