Dialog Programming - Exercise

Objective: To create transactions for creation, change and display of purchase order
header details.

Day 1
1. Copy the following tables and add your Emp. Id as a suffix(Z_*_XXXX,
inplace of XXXX use you emp. id ):
a. Z_EKKO
Fields – (Refer to EKKO for definition of fields)

Client
Purchase document Number
Company code
Vendor
Document date
Net Price
Currency

- indicates mandatory field

2. Create a transaction ZPURCR_XXXX where XXXX is your emp id, to

create purchase orders.

Layout of first screen

Purchase Order : YYYYYY

EXIT
Purchase Order No:.

Date EXIT CANCEL Net Price

Purchase Order No:

Company Code

Vendor Currency

Create Modify Display

Flow:
 YYYYYYYY will be “Create”, “Change” or “Display” depending on the
transaction.
 The “Change” and “Display” pushbuttons should be inactive when the create
transaction is called
 On pressing “Create” the details entered in “Header details” should be stored in
Z_EKKO.

Checks to be implemented:
 The PO number entered should not be present already in Z_EKKO.
 When EXIT is pressed if the user has made any input on screen then a pop-up
asking if data should be saved should appear. If “No” then user should be allowed
to exit and no checks (mandatory checks, custom checks) should take place.
 Company code – Should be a valid code found in T001.
 Vendor – Should be a vendor found in LFA1
 Currency - Should be a valid currency maintained in TCURC.

3. Create transactions for change and display also.

Create 2 transactions ZPURDIS_XXXX and ZPURCHG_XXXX, where XXXX is your

emp id.

Flow:
 YYYYYY to be either “Display” or “Change” depending on the transaction.
 Depending on the transaction the other 2 push buttons should be inactive.
 In display mode all fields must be non-editable.
 In change mode the fields will be mandatory as described in the layout earlier.

Checks to be implemented:
 The order number entered must be present in Z_EKKO.
Day 2
1. Create a screen as given below where you will use a table control to
display,change and create entries in Z_EKKO_XXXX.

Purchase Order : YYYYYY

EXIT

Purchase Date Company Code Vendor Currency Net Price

Order No.

Add Delete Select All Deselect All

Create Modify Display

Flow:
 YYYYYYYY will be “Create”, “Change” or “Display” depending on the
transaction.
 The “Modify” and “Display” pushbuttons should be inactive when the create
transaction is called.
 On pressing “Create” the details entered should be stored in Z_EKKO.
 The table control should have buttons to add a line, delete a selected line, select
all and deselect all.

Checks to be implemented:
 The PO number entered should not be present already in Z_EKKO.
 When EXIT is pressed if the user has made any input on screen then a pop-up
asking if data should be saved should appear. If “No” then user should be allowed
to exit and no checks (mandatory checks, custom checks) should take place.
 Company code – Should be a valid code found in T001.
 Vendor – Should be a vendor found in LFA1
 Currency - Should be a valid currency maintained in TCURC.
 2. Create transactions for change and display also.

Create 2 transactions ZPURDIS_XXXX and ZPURCHG_XXXX, where XXXX is your

emp id.

Flow:
 YYYYYY to be either “Display” or “Change” depending on the transaction.
 Display transaction should not have any pushbutton displayed. The “Modify”
pushbutton must be visible for the modify transaction.
 In display mode all fields must be non-editable.
 In change mode the fields will be mandatory as described in the layout earlier and
PO number should be non-editable. (Remember that when modifing table
contents the key of the table must always be non-editable)
 On pressing “Modify” the details from the table control must be updated in
Z_EKKO_XXXX table.

Checks to be implemented:
 The order numbers entered must be present in Z_EKKO.

Other general requirements:

 When any error message is raised for a field, only that field should be open for
input.
 F4 Value request is to be implemented for fields that are to be cross-checked
against standard tables.