FS-CD dunning block report
Dear all,
I need a transaction or report in FS-CD so that I can see the insurance objects and contract accounts are blocked for dunning.
Can you please help me on this
Thanks,
Latifaa
Transaction FPLKA can be used for that purpose.
regards,
bill.
Similar Messages
-
MANSP Dunning block at document level display
Dear Xperts,
I dont see the field MANSP "Dunning block" at document level (for an invoice), transaction FB03. I have chequed the field status defined for the posting key, but I cant find this field. What can be the reason the I dont see this field at document level?
Best regards.
Cristóbal.Hi,
Actually when the dunning run is executed, the documents gets the dunning block MANSP field and gets stored in table MHNK/ MHND. This block MANSP gets deleted from these tables when the dunning run is completed.
Sometimes the entry remained there, even after the dunning run completion and thus not considering customer for any next dunning run.
You can run the report RFMAHN21 in transaction SE38/ SA38 to check these blocked items.
Also check the below OSS notes if not applied in your system:-
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1005739
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1092805
Regards,
Gaurav -
Dunning Block per document number
Hi SAP Guru,
Need your help.
Scenario is like this:
We are running the dunning letter and it always gives us no output. Also, checked the Customer Master, under Correspondence tab and field for Dunning Block is empty while payment methods under u201CPayment Transactionsu201D tab is also empty which is I think it should be to run the dunning.
Upon further investigation, I found out that the invoices are tag as u201CDunning Blocku201D via FBL5N per document number. Can you explain how this happened? And why does per document number is tagged as u201CDunning Blocku201D despite the correct set up in Customer Master. And how can we delete the tag per document or is there any mass update for this.
Appreciate your thoughts on this.
Thanks,
JulieHi,
Thanks for the info. As I checked if dunning block has been tagged in SO via Header --> Accounting Tab, the field for Dunning block set to Freed for Dunning which I supposed should be.
Any other solution on this.
Thanks,
Julie -
AR Statement /Dunning Letter Report Issue
Hi Guys,
I have an issue in the Customer statement report in XMLP. There are two Concurrent Program for this Print Statement (i.e; Print Statement and Statement Generate Program) Here Print Statement runs with respect to the ARXSGPO.rdf file and Statement Generate Program runs with respect to the spawned program.
I followed the following steps to view the output in PDF using XMLP.
1. I used ARXSGPO.rdf which is from "Print Statement" Concurrent Program.
2. I have given the exact short name(ARXSGPO) of Print Statement to the Defination and Template also attachment in XMLP responsibility.
3. When i see the output after both parent (Print Statement) and child(Statement Generate Program) completed successfully. I can able to see the output only in XML format. Obvisouly it should display in PDF format right?..
Do we need any other steps to go through to achieve this AR statement report. Same issue i have with the Dunning letter report. Please drive me if any one already worked for these two reports in xmlp.
Awaiting your comments
with regards
PrabuHi Prabu,
Please refer to solution on forum:
AR Statement is not displaying PDF output where it used to display earlier.
Regards,
Gareth
Blog: http://garethroberts.blogspot.com/ -
hi,
may i know if dunning run F150 can result in dunning block?
if the maximum dunning already executed yet payment still not done, may i know where is the configuration that can make it blocked.
i tried ova8 but still not able to block.
need advice.
thanksHi
Go to FBL5N and give the customer number and execute. and select the invoice/document which has be blocked.
You can block the customer in Additional data tab of a line item for a particular customer invoice.
You can find Dunning Block item with drop down items in the box, it is the place where we can block the customer invoice my marking respective item as per the business provided their reasons.
Thanks and Regards
Sri -
Dunning Block field in Invoice Header
Hello,
There is this Dunning Block field in the invoice header tab > Accounting Data sub tab.
Please let me know how this field value is controlled. i.e. it gets determined or it flows from some master data?
Any info on this dunning block field is welcome.
Thanks,
ShankarDear Shankar
If you implement Dunning procedure, this field will be controlled based on the value you maintain in Payer customer master Company Code Data - under Correspondence tab
thanks
G. Lakshmipathi -
How to remove the Dunning block in the Invoice
Dear All,
For a particular customer, we dont have any "Dunning block" in the customer master.
But "Dunning block" enable at the invoice level. Because of this we are unable to post the document to accounting.
While releasing the document to acounting we are getting the following error.
"Reference document 92002929 000001 (Error during INSERT) Message no. VF004"
Regards,
MullairajaHi,
Try doing this way
Just Go to FBL5N look for the FI invoice, open the invoice and see the dunning block field is populated. You can unblock it by changing the document to change mode from the main menu bar.
This is the procedure to unblock/block the dunning for a customer at line item level
But in your case i am not sure the error is due to the dunning block just try
Regards,
Vassy -
Promise to Pay not creating a dunning block
Hi,
I inserted the dunning block in config in the 'Make Settings for Promise to Pay', however when I create a promise to pay 9even when its broken) the dunning block does not update the line item (where i would have expected it) nor does it update the amster record. We also have BTE 0001765
Has anyone come across this before and can you point me in the right direct for this to work, thanks
Eoinsounds like it is working according to the SAP Help from F1
Dunning Block for Items with Open Promises to Pay
Use
Has the effect that no dunning notices are sent to a business partner for an item if there is a promise to pay for the respective invoice and the promise to pay can be kept within the agreed deadline. The tolerance days are taken into account.
Dependencies
If you have entered a dunning block, during the dunning run, the system checks whether there is a promise to pay that is not overdue for the invoice of an item to be dunned. If this is so, the system excludes the item from dunning using the dunning block entered.
You can reset the dunning block when you are processing the dunning proposal. Therefore, we recommend that you create special dunning blocks for promises to pay. This enables you to differentiate these items when processing the dunning proposal.
Technical information
The integration with dunning is implemented with Business Transaction Event 00001765 (Publish and Subscribe). The event can be implemented more than once. This means that you can influence the system behavior delivered by SAP without modifications. -
Hi
I am getting a error ........
Adfvacne payment is made............This is very old advance payment....two years back
Now When we are trying to clear Advance payment it is giving an error.....advance payment document is having a dunning block.
We are not able to remove dunning block and we dont know whether error is bcox dunning block in advance payment
now to pay clear this.....please advise.
ThanksHI,
Go to T.code FD02 / XD02 an choose your Vendor , company code click on company code data (Ctrl+F2) --> click on Payment transaction Tab and remove the payment block Indicator "A"
Go to T.code : F150 And choose your Identification and enter click on Change Dunning notices (Shift+F4) and Execute (F8) Select and double click on your Payment document number and remove the payment block Indicator "A"
Thanks,
Raviteja
Edited by: Ravi Teja.T on Feb 10, 2012 5:05 AM -
Dunning Block removal from program.
Hi all,
I am creating a custom program which will be executed daily on background which has to remove dunning block.
I couldnt find any function module or such to remove dunning block.Please share your views n how it could it be done.
Best Regards,
SreeramHI Kiran..
I real time... not all the users will be having the authorization to remove the block in sales order... as sap is having standard functionalities (Like User Exits) in place to restrict the user profiles and their authorizations..
Hope this helps
Thanks,
Safeer Rahman -
Dun & Bradsteet report - 0SD_C03_DB_Q0003
Hi all,
I want to work on report based on Dun & Bradsteet report - 0SD_C03_DB_Q0003.
here i am unable to identify
0SOLD_TO__0DBCTRYCOD - D&B country
0SOLD_TO__0DBGUDUNS - D&B GU: D-U-N-S number
0SOLD_TO__0DBLGLSTAT- D&B legal form
0SOLD_TO__0DB87SIC1 - D&B US 1987 SIC Code (hierarchy)
I have installed IC -0sd_c03 and infoobjcet 0SOLD_TO. But above objects are missing.
I got to know the usage D & B. But i am unable to identify fields, tables and datasource at R/3 side.
does any worked on this report and looking for solution , how to get data for those fields.
regards,
rvcHi,
You may find information in the below links:
[D&B Customer Revenue Analysis|http://help.sap.com/saphelp_nw70/helpdata/en/8c/23bf4585334a4d97bc9179f2da7733/frameset.htm]
[Implementing D&B Vendor and Customer Analysis for SAP BW|http://help.sap.com/saphelp_nw70/helpdata/en/8c/23bf4585334a4d97bc9179f2da7733/frameset.htm]
Hope this helps...
Rgs,
Ravikanth -
please tell me the process how to create ALV block report with simple example
Try this sample program:
Program Name: ALV Program *
Description: *
Date/Author: Selvapandian *
M O D I F I C A T I O N L O G *
Date Programmer Task # Description *
REPORT ZEXAMPLE
NO STANDARD PAGE HEADING
MESSAGE-ID ZSP.
TYPE-POOLS: SLIS.
INCLUDE: .
T A B L E S *
TABLES: SCARR, "Airline
SPFLI, "Flight schedule
SBOOK. "Single Flight Booking
I N T E R N A L T A B L E S *
DATA: GT_SP_GROUPS TYPE SLIS_T_SP_GROUP_ALV WITH HEADER LINE,
GT_ZSUM TYPE SLIS_T_SORTINFO_ALV WITH HEADER LINE,
GT_FILTER TYPE SLIS_T_FILTER_ALV WITH HEADER LINE,
XHEADER TYPE SLIS_T_LISTHEADER WITH HEADER LINE.
DATA: GT_EXTAB TYPE SLIS_T_EXTAB WITH HEADER LINE.
DATA: GT_COLOR TYPE SLIS_T_SPECIALCOL_ALV WITH HEADER LINE.
DATA: BEGIN OF XDATA OCCURS 1,
CARRID LIKE SCARR-CARRID,
CARRNAME LIKE SCARR-CARRNAME,
CURRCODE LIKE SCARR-CURRCODE,
BLUBBER LIKE LTDXT-TEXT,
NUMC(3) TYPE N,
ICONS(30) TYPE C,
SYMBOLS(30) TYPE C,
AMPEL(1) TYPE C,
BOX(1) TYPE C,
LISTINFO(3) TYPE C,
END OF XDATA.
DATA: BEGIN OF YDATA OCCURS 1.
INCLUDE STRUCTURE SPFLI.
DATA: BLUBBER LIKE LTDXT-TEXT,
NUMC(3) TYPE N,
ICONS(30) TYPE C,
SYMBOLS(30) TYPE C,
AMPEL(1) TYPE C,
BOX(1) TYPE C,
LISTINFO(3) TYPE C,
COLINFO TYPE SLIS_T_SPECIALCOL_ALV,
END OF YDATA.
DATA: BEGIN OF ZDATA OCCURS 1.
INCLUDE STRUCTURE SBOOK.
DATA: BLUBBER LIKE LTDXT-TEXT,
NUMC(3) TYPE N,
ICONS(30) TYPE C,
SYMBOLS(30) TYPE C,
AMPEL(1) TYPE C,
BOX(1) TYPE C,
LISTINFO(3) TYPE C,
COLINFO TYPE SLIS_T_SPECIALCOL_ALV,
END OF ZDATA.
DATA: HDATA LIKE XDATA OCCURS 0 WITH HEADER LINE,
LDATA LIKE XDATA OCCURS 0 WITH HEADER LINE,
IDATA LIKE YDATA OCCURS 0 WITH HEADER LINE.
DATA: LFIELD TYPE SLIS_T_FIELDCAT_ALV,
XFIELD TYPE SLIS_T_FIELDCAT_ALV,
YFIELD TYPE SLIS_T_FIELDCAT_ALV,
ZFIELD TYPE SLIS_T_FIELDCAT_ALV,
HFIELD TYPE SLIS_T_FIELDCAT_ALV.
DATA: AFIELD TYPE SLIS_FIELDCAT_ALV.
DATA: GS_LAYOUT TYPE SLIS_LAYOUT_ALV,
X_LAYOUT TYPE SLIS_LAYOUT_ALV,
Y_LAYOUT TYPE SLIS_LAYOUT_ALV,
Z_LAYOUT TYPE SLIS_LAYOUT_ALV,
H_LAYOUT TYPE SLIS_LAYOUT_ALV,
L_LAYOUT TYPE SLIS_LAYOUT_ALV.
DATA: GS_KEYINFO TYPE SLIS_KEYINFO_ALV.
DATA: XISETAB TYPE SLIS_SELDIS_ALV.
DATA: GT_XEVENTS TYPE SLIS_T_EVENT,
GT_YEVENTS TYPE SLIS_T_EVENT,
GT_ZEVENTS TYPE SLIS_T_EVENT,
GT_HEVENTS TYPE SLIS_T_EVENT,
GT_LEVENTS TYPE SLIS_T_EVENT,
GT_PRINT TYPE SLIS_PRINT_ALV.
D A T A *
DATA: OK_CODE LIKE SY-UCOMM,
FLG_EXIT(1) TYPE C,
V_REPID LIKE SY-REPID,
G_EXIT,
X_SAVE,
DEFAULT,
X_VARIANT LIKE DISVARIANT,
XS_LAYOUT LIKE GS_LAYOUT,
XS_EVENT TYPE SLIS_ALV_EVENT,
GT_SPFLI LIKE SPFLI OCCURS 0 WITH HEADER LINE,
G_VARIANT LIKE DISVARIANT.
S E L E C T - O P T I O N S / P A R A M E T E R S *
SELECT-OPTIONS CARRID FOR SCARR-CARRID.
SELECTION-SCREEN SKIP.
PARAMETERS: PFSTATUS TYPE SLIS_FORMNAME DEFAULT 'PF_STATUS_SET',
HIERSEQU AS CHECKBOX DEFAULT 'X',
BOX_TABL(5) DEFAULT 'IDATA',
MAX_DATA AS CHECKBOX DEFAULT ' '.
I N I T I A L I Z A T I O N *
INITIALIZATION.
V_REPID = SY-REPID.
A T S E L E C T I O N - S C R E E N *
AT SELECTION-SCREEN ON CARRID.
IF NOT CARRID[] IS INITIAL.
SELECT SINGLE * FROM SCARR
WHERE CARRID IN CARRID.
IF SY-SUBRC <> 0.
MESSAGE E000 WITH 'Enter valid Carrier ID'(003).
ENDIF.
ENDIF.
S T A R T - O F - S E L E C T I O N *
START-OF-SELECTION.
PERFORM F_SELECTION.
PERFORM XEVENTS.
PERFORM YEVENTS.
PERFORM HEVENTS.
PERFORM FIELDS.
E N D - O F - S E L E C T I O N *
END-OF-SELECTION.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_INIT'
EXPORTING
I_CALLBACK_PROGRAM = V_REPID
I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
I_CALLBACK_PF_STATUS_SET = PFSTATUS.
X_LAYOUT-BOX_FIELDNAME = 'BOX'.
X_LAYOUT-BOX_TABNAME = 'XDATA'.
X_LAYOUT-LIGHTS_FIELDNAME = 'AMPEL'.
X_LAYOUT-INFO_FIELDNAME = 'LISTINFO'.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_APPEND'
EXPORTING
IT_FIELDCAT = XFIELD
IS_LAYOUT = X_LAYOUT
I_TABNAME = 'XDATA'
IT_EVENTS = GT_XEVENTS
I_TEXT = TEXT-0B1
TABLES
T_OUTTAB = XDATA.
IF HIERSEQU = SPACE.
y_layout-no_zebra = 'X'.
Y_LAYOUT-BOX_FIELDNAME = 'BOX'.
Y_LAYOUT-BOX_TABNAME = 'YDATA'.
Y_LAYOUT-INFO_FIELDNAME = 'LISTINFO'.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_APPEND'
EXPORTING
IT_FIELDCAT = YFIELD
IS_LAYOUT = Y_LAYOUT
I_TABNAME = 'YDATA'
IT_EVENTS = GT_YEVENTS
I_TEXT = TEXT-0B2
TABLES
T_OUTTAB = YDATA.
ELSE.
H_LAYOUT-BOX_FIELDNAME = 'BOX'.
H_LAYOUT-BOX_TABNAME = BOX_TABL.
H_LAYOUT-INFO_FIELDNAME = 'LISTINFO'.
GS_KEYINFO-HEADER01 = 'CARRID'.
GS_KEYINFO-ITEM01 = 'CARRID'.
GS_KEYINFO-ITEM02 = 'CONNID'.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_HS_APPEND'
EXPORTING
IS_LAYOUT = H_LAYOUT
IT_FIELDCAT = HFIELD
IS_KEYINFO = GS_KEYINFO
I_HEADER_TABNAME = 'HDATA'
I_ITEM_TABNAME = 'IDATA'
IT_EVENTS = GT_HEVENTS
I_TEXT = TEXT-0B2
TABLES
T_OUTTAB_HEADER = HDATA
T_OUTTAB_ITEM = IDATA.
ENDIF.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_APPEND'
EXPORTING
IT_FIELDCAT = ZFIELD
IS_LAYOUT = Z_LAYOUT
I_TABNAME = 'ZDATA'
IT_EVENTS = GT_ZEVENTS
I_TEXT = TEXT-0B3
TABLES
T_OUTTAB = ZDATA.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_APPEND'
EXPORTING
IT_FIELDCAT = LFIELD
IS_LAYOUT = L_LAYOUT
I_TABNAME = 'LDATA'
IT_EVENTS = GT_LEVENTS
I_TEXT = TEXT-0B4
TABLES
T_OUTTAB = LDATA.
GT_PRINT-RESERVE_LINES = 2.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_DISPLAY'
EXPORTING
IS_PRINT = GT_PRINT.
*& Form SELECTION
FORM F_SELECTION.
DATA: L_TABIX LIKE SY-TABIX,
LT_SBOOK LIKE SBOOK OCCURS 1 WITH HEADER LINE,
L_TABIX2 LIKE SY-TABIX.
SELECT * FROM SCARR
INTO CORRESPONDING FIELDS OF
TABLE XDATA WHERE CARRID IN CARRID.
IF SY-SUBRC <> 0.
MESSAGE E000 WITH 'No records in SCARR table'(001).
ENDIF.
IF NOT XDATA[] IS INITIAL.
SELECT * FROM SPFLI
INTO TABLE GT_SPFLI
FOR ALL ENTRIES IN XDATA
WHERE CARRID = XDATA-CARRID.
IF SY-SUBRC <> 0.
MESSAGE S000 WITH 'No records in SPFLI table'(002).
ENDIF.
ENDIF.
LOOP AT GT_SPFLI.
YDATA-NUMC = SY-TABIX DIV 5.
MOVE-CORRESPONDING GT_SPFLI TO YDATA.
APPEND YDATA.
ENDLOOP.
LOOP AT XDATA.
XDATA-NUMC = SY-TABIX DIV 4.
L_TABIX = SY-TABIX.
REFRESH GT_COLOR.
CLEAR GT_COLOR.
IF L_TABIX > 5.
XDATA-AMPEL = '1'.
ELSEIF XDATA-CURRCODE = 'USD'.
XDATA-AMPEL = '2'.
ELSE.
XDATA-AMPEL = '3'.
ENDIF.
IF XDATA-CURRCODE = 'LIT'.
GT_COLOR-FIELDNAME = 'CURRCODE'.
GT_COLOR-COLOR-COL = 6.
GT_COLOR-COLOR-INT = 0.
APPEND GT_COLOR.
XDATA-SYMBOLS = SYM_PLUS_CIRCLE.
ELSEIF XDATA-CURRCODE = 'DEM'.
GT_COLOR-COLOR-COL = 5.
GT_COLOR-COLOR-INT = 0.
APPEND GT_COLOR.
XDATA-SYMBOLS = SYM_FILLED_SQUARE.
ELSE.
GT_COLOR-FIELDNAME = 'CURRCODE'.
GT_COLOR-COLOR-COL = 7.
GT_COLOR-COLOR-INT = 1.
GT_COLOR-COLOR-INV = 1.
APPEND GT_COLOR.
XDATA-SYMBOLS = SYM_FILLED_DIAMOND.
ENDIF.
MODIFY XDATA.
ENDLOOP.
HDATA[] = XDATA[].
LDATA[] = XDATA[].
IDATA[] = YDATA[].
SELECT * FROM SBOOK
UP TO 50 ROWS.
L_TABIX = L_TABIX + 1.
L_TABIX2 = L_TABIX2 + 1.
MOVE-CORRESPONDING SBOOK TO ZDATA.
IF L_TABIX > 20.
ZDATA-CARRID = 'LH'.
ZDATA-CONNID = '47'.
ENDIF.
IF L_TABIX > 14 AND L_TABIX <= 20 OR
L_TABIX > 25.
ZDATA-FLDATE = ZDATA-FLDATE + 1.
ENDIF.
IF L_TABIX2 > 7 AND L_TABIX <= 20.
ZDATA-CONNID = 49.
ELSEIF L_TABIX >= 26.
ZDATA-CONNID = 51.
ENDIF.
IF L_TABIX2 >= 14 AND L_TABIX <= 20 .
CLEAR L_TABIX2.
ENDIF.
APPEND ZDATA.
ENDSELECT.
LOOP AT ZDATA.
L_TABIX = SY-TABIX.
IF L_TABIX = 1.
ZDATA-LOCCURAM = 520.
ENDIF.
REFRESH GT_COLOR.
CLEAR GT_COLOR.
IF ZDATA-LOCCURAM < 500.
ZDATA-AMPEL = '1'.
ELSEIF ZDATA-LOCCURAM < 530.
ZDATA-AMPEL = '2'.
ELSE.
ZDATA-AMPEL = '3'.
ENDIF.
IF ZDATA-LOCCURAM > 600.
GT_COLOR-FIELDNAME = 'LOCCURAM'.
GT_COLOR-COLOR-COL = 6.
GT_COLOR-COLOR-INT = 0.
APPEND GT_COLOR.
ZDATA-SYMBOLS = SYM_PLUS_CIRCLE.
ELSEIF ZDATA-LOCCURAM > 500.
GT_COLOR-COLOR-COL = 5.
GT_COLOR-COLOR-INT = 0.
APPEND GT_COLOR.
ZDATA-SYMBOLS = SYM_FILLED_SQUARE.
ELSE.
GT_COLOR-FIELDNAME = 'LOCCURAM'.
GT_COLOR-COLOR-COL = 7.
GT_COLOR-COLOR-INT = 1.
GT_COLOR-COLOR-INV = 1.
APPEND GT_COLOR.
ZDATA-SYMBOLS = SYM_FILLED_DIAMOND.
ENDIF.
IF ZDATA-LUGGWEIGHT = 0.
ZDATA-ICONS = ICON_INCOMPLETE.
GT_COLOR-FIELDNAME = 'LUGGWEIGHT'.
GT_COLOR-COLOR-COL = 4.
GT_COLOR-COLOR-INT = 1.
GT_COLOR-COLOR-INV = 1.
APPEND GT_COLOR.
ELSEIF ZDATA-LUGGWEIGHT < 45.
ZDATA-ICONS = ICON_CHECKED.
GT_COLOR-FIELDNAME = 'LUGGWEIGHT'.
GT_COLOR-COLOR-COL = 6.
GT_COLOR-COLOR-INT = 1.
GT_COLOR-COLOR-INV = 1.
APPEND GT_COLOR.
ELSE.
ZDATA-ICONS = ICON_FAILURE.
GT_COLOR-FIELDNAME = 'LUGGWEIGHT'.
GT_COLOR-COLOR-COL = 5.
GT_COLOR-COLOR-INT = 1.
GT_COLOR-COLOR-INV = 1.
APPEND GT_COLOR.
ENDIF.
ZDATA-NUMC = ( L_TABIX DIV 10 ) * 10.
ZDATA-COLINFO = GT_COLOR[].
IF NOT ZDATA-LUGGWEIGHT IS INITIAL.
MOVE '??' TO ZDATA-WUNIT.
ENDIF.
MODIFY ZDATA.
ENDLOOP.
IF MAX_DATA = 'X'.
DO 100 TIMES.
APPEND XDATA.
APPEND YDATA.
APPEND ZDATA.
ENDDO.
ENDIF.
ENDFORM. " SELECTION
FORM XEVENTS *
FORM XEVENTS.
CLEAR XS_EVENT.
XS_EVENT-NAME = SLIS_EV_END_OF_PAGE.
XS_EVENT-FORM = 'XEND_OF_PAGE'.
APPEND XS_EVENT TO GT_XEVENTS.
CLEAR XS_EVENT.
XS_EVENT-NAME = SLIS_EV_TOP_OF_PAGE.
XS_EVENT-FORM = 'XTOP_OF_PAGE'.
APPEND XS_EVENT TO GT_XEVENTS.
CLEAR XS_EVENT.
XS_EVENT-NAME = SLIS_EV_TOP_OF_LIST.
XS_EVENT-FORM = 'XTOP_OF_LIST'.
APPEND XS_EVENT TO GT_XEVENTS.
CLEAR XS_EVENT.
XS_EVENT-NAME = SLIS_EV_END_OF_LIST.
XS_EVENT-FORM = 'XEND_OF_LIST'.
APPEND XS_EVENT TO GT_XEVENTS.
CLEAR XS_EVENT.
ENDFORM.
FORM FIELDS *
FORM FIELDS.
DATA: L_COUNT TYPE I.
CLEAR AFIELD.
L_COUNT = L_COUNT + 1.
AFIELD-COL_POS = L_COUNT.
AFIELD-FIELDNAME = 'CARRID'.
AFIELD-REF_TABNAME = 'SCARR'.
AFIELD-KEY = 'X'. "define field as key
APPEND AFIELD TO XFIELD.
AFIELD-TABNAME = 'HDATA'.
APPEND AFIELD TO HFIELD.
AFIELD-TABNAME = 'LDATA'.
APPEND AFIELD TO LFIELD.
CLEAR AFIELD.
L_COUNT = L_COUNT + 1.
AFIELD-COL_POS = L_COUNT.
AFIELD-FIELDNAME = 'CARRNAME'.
AFIELD-REF_TABNAME = 'SCARR'.
APPEND AFIELD TO XFIELD.
AFIELD-TABNAME = 'HDATA'.
APPEND AFIELD TO HFIELD.
AFIELD-TABNAME = 'LDATA'.
APPEND AFIELD TO LFIELD.
CLEAR AFIELD.
L_COUNT = L_COUNT + 1.
AFIELD-TABNAME = 'XDATA'.
AFIELD-COL_POS = L_COUNT.
AFIELD-FIELDNAME = 'CURRCODE'.
AFIELD-REF_TABNAME = 'SCARR'.
AFIELD-INPUT = INPUT.
APPEND AFIELD TO XFIELD.
AFIELD-TABNAME = 'HDATA'.
APPEND AFIELD TO HFIELD.
AFIELD-TABNAME = 'LDATA'.
APPEND AFIELD TO LFIELD.
CLEAR AFIELD.
L_COUNT = L_COUNT + 1.
AFIELD-TABNAME = 'XDATA'.
AFIELD-COL_POS = L_COUNT.
AFIELD-FIELDNAME = 'NUMC'.
AFIELD-DATATYPE = 'NUMC'.
AFIELD-REPTEXT_DDIC = TEXT-001.
AFIELD-INPUT = INPUT.
AFIELD-DO_SUM = 'X'.
APPEND AFIELD TO XFIELD.
AFIELD-TABNAME = 'HDATA'.
APPEND AFIELD TO HFIELD.
AFIELD-TABNAME = 'LDATA'.
APPEND AFIELD TO LFIELD.
CLEAR AFIELD.
L_COUNT = 0.
L_COUNT = L_COUNT + 1.
AFIELD-COL_POS = L_COUNT.
AFIELD-TABNAME = SPACE.
AFIELD-FIELDNAME = 'CARRID'.
AFIELD-REF_TABNAME = 'SPFLI'.
AFIELD-KEY = 'X'. "define field as key
APPEND AFIELD TO YFIELD.
AFIELD-TABNAME = 'IDATA'.
APPEND AFIELD TO HFIELD.
CLEAR AFIELD.
L_COUNT = L_COUNT + 1.
AFIELD-TABNAME = SPACE.
AFIELD-COL_POS = L_COUNT.
AFIELD-FIELDNAME = 'CONNID'.
AFIELD-REF_TABNAME = 'SPFLI'.
AFIELD-KEY = 'X'. "define field as key
AFIELD-KEY_SEL = 'X'.
APPEND AFIELD TO YFIELD.
AFIELD-TABNAME = 'IDATA'.
APPEND AFIELD TO HFIELD.
CLEAR AFIELD.
L_COUNT = L_COUNT + 1.
AFIELD-TABNAME = SPACE.
AFIELD-COL_POS = L_COUNT.
AFIELD-FIELDNAME = 'CITYFROM'.
AFIELD-REF_TABNAME = 'SPFLI'.
APPEND AFIELD TO YFIELD.
AFIELD-TABNAME = 'IDATA'.
APPEND AFIELD TO HFIELD.
CLEAR AFIELD.
L_COUNT = L_COUNT + 1.
AFIELD-TABNAME = SPACE.
AFIELD-COL_POS = L_COUNT.
AFIELD-FIELDNAME = 'AIRPFROM'.
AFIELD-REF_TABNAME = 'SPFLI'.
APPEND AFIELD TO YFIELD.
AFIELD-TABNAME = 'IDATA'.
APPEND AFIELD TO HFIELD.
CLEAR AFIELD.
L_COUNT = L_COUNT + 1.
AFIELD-TABNAME = SPACE.
AFIELD-COL_POS = L_COUNT.
AFIELD-FIELDNAME = 'CITYTO'.
AFIELD-REF_TABNAME = 'SPFLI'.
APPEND AFIELD TO YFIELD.
AFIELD-TABNAME = 'IDATA'.
APPEND AFIELD TO HFIELD.
CLEAR AFIELD.
L_COUNT = L_COUNT + 1.
AFIELD-TABNAME = SPACE.
AFIELD-COL_POS = L_COUNT.
AFIELD-FIELDNAME = 'AIRPTO'.
AFIELD-REF_TABNAME = 'SPFLI'.
APPEND AFIELD TO YFIELD.
AFIELD-TABNAME = 'IDATA'.
APPEND AFIELD TO HFIELD.
CLEAR AFIELD.
L_COUNT = L_COUNT + 1.
AFIELD-TABNAME = SPACE.
AFIELD-COL_POS = L_COUNT.
AFIELD-FIELDNAME = 'DEPTIME'.
AFIELD-REF_TABNAME = 'SPFLI'.
APPEND AFIELD TO YFIELD.
AFIELD-TABNAME = 'IDATA'.
APPEND AFIELD TO HFIELD.
CLEAR AFIELD.
L_COUNT = L_COUNT + 1.
AFIELD-TABNAME = SPACE.
AFIELD-COL_POS = L_COUNT.
AFIELD-FIELDNAME = 'ARRTIME'.
AFIELD-REF_TABNAME = 'SPFLI'.
APPEND AFIELD TO YFIELD.
AFIELD-TABNAME = 'IDATA'.
APPEND AFIELD TO HFIELD.
CLEAR AFIELD.
L_COUNT = L_COUNT + 1.
AFIELD-TABNAME = SPACE.
AFIELD-COL_POS = L_COUNT.
AFIELD-FIELDNAME = 'FLTIME'.
AFIELD-REF_TABNAME = 'SPFLI'.
AFIELD-NO_OUT = 'X'.
APPEND AFIELD TO YFIELD.
AFIELD-TABNAME = 'IDATA'.
APPEND AFIELD TO HFIELD.
CLEAR AFIELD.
L_COUNT = L_COUNT + 1.
AFIELD-TABNAME = SPACE.
AFIELD-COL_POS = L_COUNT.
AFIELD-FIELDNAME = 'FLTYPE'.
AFIELD-REF_TABNAME = 'SPFLI'.
AFIELD-NO_OUT = 'X'.
APPEND AFIELD TO YFIELD.
AFIELD-TABNAME = 'IDATA'.
APPEND AFIELD TO HFIELD.
Ikonen
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-COL_POS = L_COUNT.
AFIELD-TABNAME = SPACE.
AFIELD-FIELDNAME = 'ICONS'.
AFIELD-REF_TABNAME = ' '.
AFIELD-SP_GROUP = 'B'.
AFIELD-REPTEXT_DDIC = 'Gpk?'(045).
AFIELD-NO_OUT = 'X'.
AFIELD-ICON = 'X'.
AFIELD-DATATYPE = 'CHAR'.
AFIELD-OUTPUTLEN = '4'.
APPEND AFIELD TO YFIELD.
AFIELD-TABNAME = 'IDATA'.
APPEND AFIELD TO HFIELD.
Symbole
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
L_COUNT = L_COUNT + 1.
AFIELD-TABNAME = SPACE.
AFIELD-FIELDNAME = 'SYMBOLS'.
AFIELD-REF_TABNAME = ' '.
AFIELD-COL_POS = L_COUNT.
AFIELD-REPTEXT_DDIC = 'Prs?'(040).
AFIELD-SP_GROUP = 'B'.
AFIELD-NO_OUT = 'X'.
AFIELD-SYMBOL = 'X'.
AFIELD-DATATYPE = 'CHAR'.
AFIELD-OUTPUTLEN = '4'.
AFIELD-JUST = 'C'.
APPEND AFIELD TO YFIELD.
AFIELD-TABNAME = 'IDATA'.
APPEND AFIELD TO HFIELD.
Gepäckgewicht
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
L_COUNT = L_COUNT + 1.
AFIELD-TABNAME = SPACE.
AFIELD-SP_GROUP = 'A'.
AFIELD-NO_OUT = SPACE.
AFIELD-FIELDNAME = 'DISTANCE'.
AFIELD-REF_TABNAME = 'SPFLI'.
AFIELD-COL_POS = L_COUNT.
AFIELD-NO_SIGN = 'X'.
AFIELD-QFIELDNAME = 'DISTID'.
AFIELD-OUTPUTLEN = '10'.
APPEND AFIELD TO YFIELD.
AFIELD-TABNAME = 'IDATA'.
APPEND AFIELD TO HFIELD.
Mengeneinheit
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
L_COUNT = L_COUNT + 1.
AFIELD-TABNAME = SPACE.
AFIELD-SP_GROUP = 'A'.
AFIELD-NO_OUT = SPACE.
AFIELD-FIELDNAME = 'DISTID'.
AFIELD-REF_TABNAME = 'SPFLI'.
AFIELD-COL_POS = L_COUNT.
AFIELD-OUTPUTLEN = '4'.
APPEND AFIELD TO YFIELD.
AFIELD-TABNAME = 'IDATA'.
APPEND AFIELD TO HFIELD.
Numc
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-COL_POS = L_COUNT.
AFIELD-TABNAME = SPACE.
AFIELD-FIELDNAME = 'NUMC'.
AFIELD-COL_POS = L_COUNT.
AFIELD-DO_SUM = 'X'.
AFIELD-SP_GROUP = 'S'.
AFIELD-SELTEXT_S = 'NUMC'.
AFIELD-SELTEXT_M = 'NUMC_U'.
AFIELD-SELTEXT_L = 'NUMC_USER'(041).
AFIELD-DATATYPE = 'NUMC'.
AFIELD-OUTPUTLEN = '10'.
AFIELD-NO_OUT = SPACE.
APPEND AFIELD TO YFIELD.
AFIELD-TABNAME = 'IDATA'.
APPEND AFIELD TO HFIELD.
Blubber
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-COL_POS = L_COUNT.
AFIELD-TABNAME = SPACE.
AFIELD-FIELDNAME = 'BLUBBER'.
AFIELD-REF_TABNAME = 'LTDXT'.
AFIELD-REF_FIELDNAME = 'TEXT'.
AFIELD-COL_POS = L_COUNT.
AFIELD-HOTSPOT = 'X'.
AFIELD-SP_GROUP = 'S'.
AFIELD-REPTEXT_DDIC = 'Kommentar'(043).
AFIELD-DATATYPE = 'CHAR'.
AFIELD-OUTPUTLEN = '20'.
AFIELD-NO_OUT = 'X'.
APPEND AFIELD TO YFIELD.
AFIELD-TABNAME = 'IDATA'.
APPEND AFIELD TO HFIELD.
Key
L_COUNT = 0.
CLEAR AFIELD.
AFIELD-FIELDNAME = 'CARRID'.
AFIELD-OUTPUTLEN = '3'.
AFIELD-KEY = 'X'.
AFIELD-REF_TABNAME = 'SBOOK'.
AFIELD-COL_POS = L_COUNT.
AFIELD-OFFSET = '4'.
APPEND AFIELD TO ZFIELD.
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-FIELDNAME = 'FLDATE'.
AFIELD-KEY = 'X'.
AFIELD-KEY_SEL = 'X'.
AFIELD-REF_TABNAME = 'SBOOK'.
AFIELD-COL_POS = L_COUNT.
APPEND AFIELD TO ZFIELD.
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-FIELDNAME = 'CONNID'.
AFIELD-KEY = 'X'.
AFIELD-KEY_SEL = 'X'.
AFIELD-REF_TABNAME = 'SBOOK'.
AFIELD-COL_POS = L_COUNT.
APPEND AFIELD TO ZFIELD.
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-FIELDNAME = 'BOOKID'.
AFIELD-KEY_SEL = 'X'.
AFIELD-KEY = 'X'.
AFIELD-REF_TABNAME = 'SBOOK'.
AFIELD-COL_POS = L_COUNT.
APPEND AFIELD TO ZFIELD.
Ikonen
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-FIELDNAME = 'ICONS'.
AFIELD-REF_TABNAME = ' '.
AFIELD-SP_GROUP = 'B'.
AFIELD-COL_POS = L_COUNT.
AFIELD-REPTEXT_DDIC = 'Gpk?'(045).
AFIELD-NO_OUT = 'X'.
AFIELD-ICON = 'X'.
AFIELD-DATATYPE = 'CHAR'.
AFIELD-OUTPUTLEN = '4'.
APPEND AFIELD TO ZFIELD.
Buchungsdatum
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-FIELDNAME = 'ORDER_DATE'.
AFIELD-REF_TABNAME = 'SBOOK'.
AFIELD-COL_POS = L_COUNT.
AFIELD-SP_GROUP = 'S'.
APPEND AFIELD TO ZFIELD.
Kundentyp
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-FIELDNAME = 'CUSTTYPE'.
AFIELD-REF_TABNAME = 'SBOOK'.
AFIELD-COL_POS = L_COUNT.
AFIELD-SP_GROUP = 'S'.
APPEND AFIELD TO ZFIELD.
Kundennummer
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-FIELDNAME = 'CUSTOMID'.
AFIELD-REF_TABNAME = 'SBOOK'.
AFIELD-COL_POS = L_COUNT.
AFIELD-SP_GROUP = 'S'.
AFIELD-OUTPUTLEN = '3'.
APPEND AFIELD TO ZFIELD.
Raucher
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-FIELDNAME = 'SMOKER'.
AFIELD-REF_TABNAME = 'SBOOK'.
AFIELD-COL_POS = L_COUNT.
AFIELD-SP_GROUP = 'S'.
APPEND AFIELD TO ZFIELD.
Flugklasse
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-FIELDNAME = 'CLASS'.
AFIELD-REF_TABNAME = 'SBOOK'.
AFIELD-COL_POS = L_COUNT.
AFIELD-SP_GROUP = 'S'.
APPEND AFIELD TO ZFIELD.
Rechnungsstellung ja/nein
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-FIELDNAME = 'INVOICE'.
AFIELD-REF_TABNAME = 'SBOOK'.
AFIELD-COL_POS = L_COUNT.
AFIELD-SP_GROUP = 'S'.
AFIELD-NO_OUT = 'X'.
APPEND AFIELD TO ZFIELD.
Symbole
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-FIELDNAME = 'SYMBOLS'.
AFIELD-REF_TABNAME = ' '.
AFIELD-COL_POS = L_COUNT.
AFIELD-REPTEXT_DDIC = 'Prs?'(040).
AFIELD-SP_GROUP = 'B'.
AFIELD-NO_OUT = 'X'.
AFIELD-SYMBOL = 'X'.
AFIELD-DATATYPE = 'CHAR'.
AFIELD-OUTPUTLEN = '4'.
AFIELD-JUST = 'C'.
APPEND AFIELD TO ZFIELD.
Betrag
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-FIELDNAME = 'LOCCURAM'.
AFIELD-REF_TABNAME = 'SBOOK'.
AFIELD-SP_GROUP = 'H'.
AFIELD-COL_POS = L_COUNT.
AFIELD-CFIELDNAME = 'LOCCURKEY'.
AFIELD-DATATYPE = 'CURR'.
AFIELD-DO_SUM = 'X'.
AFIELD-OUTPUTLEN = '10'.
APPEND AFIELD TO ZFIELD.
Währung
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-FIELDNAME = 'LOCCURKEY'.
AFIELD-TECH = ' '.
AFIELD-REF_TABNAME = 'SBOOK'.
AFIELD-COL_POS = L_COUNT.
AFIELD-OUTPUTLEN = '4'.
AFIELD-SP_GROUP = 'H'.
APPEND AFIELD TO ZFIELD.
BetragFW
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-FIELDNAME = 'FORCURAM'.
AFIELD-REF_TABNAME = 'SBOOK'.
AFIELD-SP_GROUP = 'F'.
AFIELD-COL_POS = L_COUNT.
AFIELD-NO_OUT = 'X'.
AFIELD-DO_SUM = 'X'.
AFIELD-CFIELDNAME = 'FORCURKEY'.
AFIELD-DATATYPE = 'CURR'.
AFIELD-OUTPUTLEN = '10'.
APPEND AFIELD TO ZFIELD.
Währung
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-FIELDNAME = 'FORCURKEY'.
AFIELD-SP_GROUP = 'F'.
AFIELD-TECH = ' '.
AFIELD-REF_TABNAME = 'SBOOK'.
AFIELD-COL_POS = L_COUNT.
AFIELD-NO_OUT = 'X'.
AFIELD-OUTPUTLEN = '4'.
APPEND AFIELD TO ZFIELD.
Gepäckgewicht
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-SP_GROUP = 'A'.
AFIELD-NO_OUT = 'X'.
AFIELD-FIELDNAME = 'LUGGWEIGHT'.
AFIELD-REF_TABNAME = 'SBOOK'.
AFIELD-COL_POS = L_COUNT.
AFIELD-NO_SIGN = 'X'.
AFIELD-QFIELDNAME = 'WUNIT'.
AFIELD-OUTPUTLEN = '10'.
APPEND AFIELD TO ZFIELD.
Mengeneinheit
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-SP_GROUP = 'A'.
AFIELD-NO_OUT = 'X'.
AFIELD-FIELDNAME = 'WUNIT'.
AFIELD-REF_TABNAME = 'SBOOK'.
AFIELD-COL_POS = L_COUNT.
AFIELD-OUTPUTLEN = '4'.
APPEND AFIELD TO ZFIELD.
Numc
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-FIELDNAME = 'NUMC'.
AFIELD-COL_POS = L_COUNT.
AFIELD-SP_GROUP = 'S'.
AFIELD-SELTEXT_S = 'NUMC'.
AFIELD-SELTEXT_M = 'NUMC_U'.
AFIELD-SELTEXT_L = 'NUMC_USER'(041).
AFIELD-DATATYPE = 'NUMC'.
AFIELD-OUTPUTLEN = '10'.
AFIELD-NO_OUT = 'X'.
APPEND AFIELD TO ZFIELD.
Blubber
L_COUNT = L_COUNT + 1.
CLEAR AFIELD.
AFIELD-FIELDNAME = 'BLUBBER'.
AFIELD-REF_TABNAME = 'LTDXT'.
AFIELD-REF_FIELDNAME = 'TEXT'.
AFIELD-COL_POS = L_COUNT.
AFIELD-HOTSPOT = 'X'.
AFIELD-SP_GROUP = 'S'.
AFIELD-REPTEXT_DDIC = 'Kommentar'(043).
AFIELD-DATATYPE = 'CHAR'.
AFIELD-OUTPUTLEN = '20'.
AFIELD-NO_OUT = 'X'.
APPEND AFIELD TO ZFIELD.
ENDFORM. " FIELDS
FORM YEVENTS *
FORM YEVENTS.
CLEAR XS_EVENT.
XS_EVENT-NAME = SLIS_EV_END_OF_PAGE.
XS_EVENT-FORM = 'YEND_OF_PAGE'.
APPEND XS_EVENT TO GT_YEVENTS.
CLEAR XS_EVENT.
XS_EVENT-NAME = SLIS_EV_TOP_OF_PAGE.
XS_EVENT-FORM = 'YTOP_OF_PAGE'.
APPEND XS_EVENT TO GT_YEVENTS.
CLEAR XS_EVENT.
XS_EVENT-NAME = SLIS_EV_TOP_OF_LIST.
XS_EVENT-FORM = 'YTOP_OF_LIST'.
APPEND XS_EVENT TO GT_YEVENTS.
CLEAR XS_EVENT.
XS_EVENT-NAME = SLIS_EV_END_OF_LIST.
XS_EVENT-FORM = 'YEND_OF_LIST'.
APPEND XS_EVENT TO GT_YEVENTS.
ENDFORM.
FORM HEVENTS *
FORM HEVENTS.
CLEAR XS_EVENT.
XS_EVENT-NAME = SLIS_EV_TOP_OF_PAGE.
XS_EVENT-FORM = 'HTOP_OF_PAGE'.
APPEND XS_EVENT TO GT_HEVENTS.
CLEAR XS_EVENT.
XS_EVENT-NAME = SLIS_EV_TOP_OF_LIST.
XS_EVENT-FORM = 'HTOP_OF_LIST'.
APPEND XS_EVENT TO GT_HEVENTS.
CLEAR XS_EVENT.
XS_EVENT-NAME = SLIS_EV_END_OF_LIST.
XS_EVENT-FORM = 'HEND_OF_LIST'.
APPEND XS_EVENT TO GT_HEVENTS.
ENDFORM.
FORM ZBEFORE_LINE_OUTPUT USING LINEINFO TYPE SLIS_LINEINFO.
WRITE AT /20 'HalloZ'.
ENDFORM.
FORM XBEFORE_LINE_OUTPUT *
FORM XBEFORE_LINE_OUTPUT USING LINEINFO TYPE SLIS_LINEINFO.
WRITE AT /20 'HalloX'.
ENDFORM.
FORM XTOP_OF_PAGE *
FORM XTOP_OF_PAGE.
WRITE: / 'X_TOP_OF_PAGE'.
ENDFORM.
FORM XTOP_OF_LIST *
FORM XTOP_OF_LIST.
WRITE: / 'X_TOP_OF_LIST'.
ENDFORM.
FORM XEND_OF_PAGE *
FORM XEND_OF_PAGE.
WRITE: / 'X_END_OF_PAGE'.
ENDFORM.
FORM XEND_OF_LIST *
FORM XEND_OF_LIST.
WRITE: / 'X_END_OF_LIST'.
ENDFORM.
FORM YTOP_OF_PAGE.
WRITE: / 'Y_TOP_OF_PAGE'.
ENDFORM.
FORM YTOP_OF_LIST *
FORM YTOP_OF_LIST.
WRITE: / 'Y_TOP_OF_LIST'.
ENDFORM.
FORM YEND_OF_PAGE *
FORM YEND_OF_PAGE.
WRITE: / 'Y_END_OF_PAGE'.
ENDFORM.
FORM YEND_OF_LIST *
FORM YEND_OF_LIST.
WRITE: / 'Y_END_OF_LIST'.
ENDFORM.
FORM YTOP_OF_LIST *
FORM HTOP_OF_LIST.
WRITE: / 'h_TOP_OF_LIST'.
ENDFORM.
FORM YEND_OF_PAGE *
FORM HEND_OF_PAGE.
WRITE: / 'h_END_OF_PAGE'.
ENDFORM.
FORM YEND_OF_LIST *
FORM HEND_OF_LIST.
WRITE: / 'h_END_OF_LIST'.
ENDFORM.
FORM USER_COMMAND USING R_UCOMM LIKE SY-UCOMM
RS_SELFIELD TYPE SLIS_SELFIELD.
CASE R_UCOMM.
WHEN 'REFR'.
LOOP AT XDATA.
IF XDATA-BOX = 'X'.
XDATA-LISTINFO = 'C50'.
ELSE.
XDATA-LISTINFO = SPACE.
ENDIF.
MODIFY XDATA.
ENDLOOP.
LOOP AT YDATA.
IF YDATA-BOX = 'X'.
YDATA-LISTINFO = 'C50'.
ELSE.
YDATA-LISTINFO = SPACE.
ENDIF.
MODIFY YDATA.
ENDLOOP.
LOOP AT IDATA.
IF IDATA-BOX = 'X'.
IDATA-LISTINFO = 'C50'.
ELSE.
IDATA-LISTINFO = SPACE.
ENDIF.
MODIFY IDATA.
ENDLOOP.
RS_SELFIELD-REFRESH = 'X'.
WHEN OTHERS.
ENDCASE.
ENDFORM.
FORM PF_STATUS_SET *
FORM PF_STATUS_SET USING EXTAB TYPE SLIS_T_EXTAB.
SET PF-STATUS 'STANDARD'. " EXCLUDING EXTAB.
ENDFORM.. -
Dunning Block - Because of a previous Dunning Run
Hi All,
1. When we try to run Dunning, we found that Some accounts are being blocked because of some previous Dunning Run( Identification ABC dt 01.01.2007),
2. When I check those dunning runs(Identification ABC dt 01.01.2007), i see in status, Dunning run and printout executed, job deleted.
3. When I check the customer master, the last dun date is not same as in the step two.
4. so I am unable to find out the problem, why the accounts are not being dunned?
can anyone pl help me with this issue.
Thanks
AKHi
Thanks for the response.
I have checked, there is no dunning block either in the master or in the open items.
Also, the items are over due, by 18 days,
And our dunning is as follows
Dun level 1 1 Days
Dun level 2 15 days
Dun level 3 30 Days
Dun level 4 45 Days
So that means the items are overdue, and should be dunned, but the message says its blocked becuase of the previous dun run.
Thanks
AK -
Dunning block for document is appearing in printout
Hi SAP folks,
I have 100 open due items in customer account. I was executing dunning in F150 for that customer, it is showing 100 line items in dunning notice.
Here my question is that, i want to put dunning block for one document. So, i went to change dunning notice and put dun block for required document. Now i am checking dunning list and it is not appearing...upto here system performing correctly because i kept dunning block.
The problem is now when i am taking dun sample printout/dun print out total 100 line items are appearing whereas this will be wrong, dun printout shoud show only 99 items because i kept one doc in dun block. This is happening for only this customer. When i am executing for other cusomters it is performing currectly and have no issues.
Why this is happening to that customer? I have checked master data also. Please can anybody help me in this tricky issue
Regards
VKResolved myself....
-
Dunning Block for Customer Disputed objects
Dear Colleagues,
I come with what seems to be a simple but interesting requirement from my customer, that I believe can turn out to be an interesting subject for discussion and knowledge exchange.
My customer requires having the possibility of creating several dispute cases, at different times with different partial amounts and different reasons, related to the same invoice. This is possible only through u201Ccustomer disputed amountu201D. With this functionality I can create several disputes linked to the same invoice, with partial amounts and different reasons.
The tricky part comes when the requirement also asks for automatic dunning block for the invoice, for each one of the dispute cases. Here I face with two basic problems:
1) There is only one dunning block at invoice level. (an invoice cannot have several dunning block reasons at the same time.
2) The automatic document changes through dispute cases is not for "customer disputed objects". It only creates and updates the dunning blocks on invoices that belong to a traditional dispute case ("Disputed Objects").
Has anyone faced a similar requirement before? any insights or suggestions regarding this process?
Thank you very much
Best Regards,
Luis AngeliHi Luis,
Customer disputed objects are meant to capture customer disputes prior to the receipt of payment.
They can be used to create many disputes for a single invoice.
However a single invoice can only be disputed once.
Further to this, if different parts of an invoice are disputed, the dunning block should only be removed once all issues against the invoice are resolved.
It could be an idea to create a single dispute against an invoice, and then get different people to resolve the different issues.
You may also want to consider how you are creating your invoices - it could be that you split them down further so there is only a single dispute against an invioce.
Maybe you are looking for
-
No audio Mac Pro after installing OS 10.7.5 Update 1163
No audio on Mac Pro after installing OS 10.7.5 Update 11G63. Tried uninstalling iTunes Dock Notifications but it wasn't installed in the first place. No Audio on iTunes, youTube, Chrome, etc.
-
My Iphone stolen Is it possible to disable it by serial number
my Iphone stolen Is it possible to disable it by serial number or Appl co?
-
Multi Database Support: TimeQuery setting for non-oracle
Hello, I wanted to develop ADF Application which is database-neutral and thus SQL92 type application. I actually wanted to make sure that my application runs fine at least on MySQL DB. Therefore I set up my connection in JDeveloper to Mysql database
-
Hi - I'm using WL 10.0 which will host some MDBs (possibly EJB 3.0) to consume messages - these MDBs need to digest messages from a foreign JMS provider - in our case we need to connect to IBM MQ 6.0 Queue Manager hosted on a remote machine elsewhere
-
Opening "Preferences" folder will crash the Finder every time!
On my 24" iMac with OSX 10.6.5, opening User's "Preferences" folder will crash the Snow Leopard Finder every time! This will happen even if I try to open a saved "Preferences" folder on an external drive. On the brand-new 27" iMac also with OSX 10.6.