Proxy not Triggered on ECC

Hi Experts
I am working on a File to Proxy scenario, Messages are being sent to ECC after content conversion sucessfully however the Proxy (Method) is not getting triggered on ECC
Looks like all the messages are sitting in some queue on ECC ,
Can anyone please let me know how to triggere the messages that are being stuck on ECC and clear out them, to process sucessfully
Thanks
PR

When I checked the message which is schduled on ECC have the following error message
Please enter 8th, 9th and 10th digits between 000 and 999 in the format of '000'
This must be data inconsistency while updating data in ECC system. There might be some validation defined on some field for which the system is expecting 000 to 999 value. Please check with your ABAP and Functional teams for which field the validation is defined and check your xml payload as well.
And also ask your ABAP team to debug with the payload generated in ECC system.
Also check your queues are registered in ECC or not. If not then register and check.
Regards,
Naushi

Similar Messages

Migrated BADI Implementation not triggering in ECC 6.0

Hi Experts,
Need your urgent assistance how to deal with migrated BADI implementation which is not triggering in ECC 6.0. This is for PO (ME_PROCESS_PO_CUST). In the original version (4.6) it was working fine. But when this is migrated to ECC 6.0, it's not firing. Please help to trigger this one in ECC 6.0.
Points will be awarded and thanks in advance,
LM

Hi LM,
Can you just paste the code in the BADI.(The method in which code is there)
Is this BADI implemented and in the Active status.
Check in SE19 if the implementation exist or not?
There may be chances that some condition is not met which can trigger this BADI. Have you read the documentation of the BADI?
Regards,
Atish

Central Contract Mngt: Contract Confirmation Out not triggering from ECC

Hi,
Can some one take a look at this and let me know if you have any suggestions
After following note 1268821 we have Contracts replicating from SRM to ECC via PI. However we are not getting the Contract Replication Confirmation Out triggering from ECC to SRM The configuration in PI is waiting to receive PurchasingContractSRMReplicationConfirmation_Out from ECC for delivery to PurchasingContractSRMReplicationConfirmation_In in SRM.
Does anyone know what we maybe missing, perhaps a setting in ECC that will trigger the Confirmation Out to SRM?
Any help much appreciated.
Che

Just an update.
It turns out that ECC is generating message PurchasingContractERPConfirmation_Out which is contrary to what we are expecting PurchasingContractSRMReplicationConfirmation_Out.
Have logged it with SAP support for now.

Mailer Program Not Triggering Mail in ECC 6.0

Hi Experts,
We have upgarded from 4.6b to ECC 6.0,
In an program we are using function module
SO_NEW_DOCUMENT_ATT_SEND_API1
It was working fine 4.6b but In ECC it is not triggering mail to an internet address mentioned.
In SBWP I can see the mail in the out box, but the mail details are not appearing in SOST transaction.
Does any more specific setting required.
Even I am not getting any Exceptions while running the FM.
Thanks in Advacne,
Regards,
IFF

Hi,
Check if commit_work parameter of ur func module = 'X'.
Check the sy-subrc value after the FM.
In SOST in send status tab check all the check boxes n execute
in ur program add this piece of code...just below the FM SO_NEW_........
If sy-subrc = 0.
wait up to 1 seconds.
submit rsconn01 with mode = 'INT' and return.
endif.
Cheers,
jose.

Deep XSD's structure not reflecting in ECC - Proxy code

Dear forum members,
Deep XSD's structure not reflecting in ECC - Proxy code. any suggestion please..
With the help of XSD able to create service Interface - Outbound in PI, the complete structure is visible in PI but in ECC ( Tcode - Sproxy ) unable to view complete structure, top two nodes are visible remaining not reflecting in the ECC system.
Cheers
Rocky

Hi Rocky ,
Regenerate proxy in ECC and check again , structure will reflect.
Note : Whenever we make changes(adding new fields or deletion of existing fields) to Data type / ED in PI . You have to generate the proxy structure (outbound or Inbound) in ECC and activate. Then changes will be reflected in Proxy also.
Thanks
Hari.

PO XML proxy is triggered twice from ECC to SUS

Dear Experts,
We are using Classical scenario. Once a shopping cart is created and approved a PO will be created in ECC through PI and corresponding SUS PO will be created in SUS system, It will be triggered from ECC. when we check in SXMB_MONI transaction. There are 2 proxy genetared to SUS. Actually only one should trigger.
Kindly guide how it can be checked.
Thanks & Regards
Arun.K.P

Hi jackytam ,
/people/yeusheng.teo/blog/2008/01/05/ordering-unit-vs-order-pricing-unit-in-srm-sus
you make get some pointers
regards,
Neelima

Alert 7055 - Manual Approval Required, XML messages to ECC not Triggered.

Hi All,
I have a behavior in our Client Production System.
We have setup a process in which if a PO confirmation Dates are -5 / + 5 days appart then that line item should result in Manual Approval Required.
Even though a PO line item is in Status "Manual Approval Required" a XML message is triggered and a AB confirmation gets created in ECC.
Issue we faced:- even if the Confirmation Dates are within range still the PO was ending up in Manual Approval specially if vendor enters multiple Schedule lines for the same PO line item with Dates with in +/- 5 days.
In our Test system , we implemented notes given by SAP to fix the above issue the issue looks fixed but,
Now the behavior is if the line item is having Status "Manual Approval Required", NO XML messages are getting triggered for a PO with Confirmation date beyond +/- 5 days. Once the the approval is given and Schedule line is Adopted the XML is getting triggered correctly.
I want to know from all the Experts on to understand which behavior is correct is Production correct(excluding the Bug) or the Test systems not triggering XML unless the Manual Approval is given.
I did read SAP help but i am not understanding since SAP mentions both behavior not Clear when such behavior should occur.
Please help to understand thsi behavior.
Please advise.
Thx
MJ

Hi MJ,
The behaviour in your Test system is correct.
When there is Manual approval is required which means deviation from requested which first needs to be accepted by customer in SNC.
If Purchase order item status is Manual approval required and XML's are getting trigger which updates ECC with AB-confirmation then customer will assume PO is confirmed without deviation until he/she compares requested schedule line and confirmed schedule line.
SAP standard behaviour is also same as your Test system behaviour see the help link(In process point#6)
http://help.sap.com/saphelp_snc70/helpdata/EN/48/1010953b2b3558e10000000a42189d/content.htm
Regards,
Nikhil

PO Response mail not triggering in SRM SUS

Hi,
We are on SRM7 wtih ECC 6, When user click on Process, Confirm all and Send for a PO from SUS corresponding XML "PurchaseOrderConfirmation_Out" not triggered in SRM.
with the same settings in Dev and Quality xml triggered successfully but not in PRD
If any one come accross the same issue, please share the solution.
Regards,

I think the shopping cart must be waiting for some approvals...
Please check the workflow log of the shopping cart...
PO will be created..once the shopping cart is released....

Outbound Proxy is triggered from CRM 4.0, tag is missing in the payload

Hi,
A Outbound Proxy is triggered from CRM 4.0, one of the tag is missing in the payload. I had checked the SXMB_MONI in CRM and in XI as well both seems to miss that. I checked the BADI which triggers this PROXY the data is rightly populated to the PROXY method. Also, this problem is not occuring regularly but few times it misses the same tag. The occurrance defined in the datatype is 0 to 1. Can anyone help why this is happening..
Many Thanks..

This could rather be a logical error. May be the logic is not populating the XML tag on those occassions. I would suggest to debug in that direction.
VJ

ABAP Proxy - Message prioritizing in ECC

Dear Experts,
Can you provide me any document to prioritize the proxy messages in Application Engine (ECC - SMQ2). I've already gone through the document for Integration Server but I need the one more specific for the Application Engine and more details like configuring specific queue sets for individual interfaces. Please help.
Thanks,

Hi,
The queue used for Proxy call is not registerd in ECC system. You need to register the queue to process successfully.
you will get the name of Queue from SMQ2 t-code and register it with t-code SMQR.
Thanks
Swarup
Edited by: Swarup Sawant on Aug 24, 2009 8:03 AM

MB_DOCUMENT_BADI not triggring in ECC 6.0 version

Hi All,
We are upgrading our SAP R3 from 4.6c to ECC 6.0.
In the new system, Transaction SE18 now has two options
1. Enhancement spot
2. BAdI Name
When I display my BADI MB_DOCUMENT_BADI
Attributes tab shows BAdI migrates to enhancement spot MB_GOODSMOVEMENT
When I display Enhancement spot Technical details Tab shows Enhancement Implementation Status shows "Initial".
We have implemented this BADI in our 4.6c version. And its triggering when I run MIGO transaction.
In the new system BADI is not triggering when I run the MIGO.
Above is the only difference I found in the new system when compared with our old system settings.
Can any one suggest me what all the things I need to take care to get working this BADI
Thanks,
Satish

Hi
Also please read this.
Business Add-In: Create a Material Document
Business add-ins when creating a material document
The enhancement MB_DOCUMENT_BADI has two methods that are called up by the same interface, though at different times. All material document data from the following tables is transferred to this business add-in:
MKPF (material document header)
MSEG (material document items)
VM07M (update data)
This data can be used in other programs, but cannot be changed.
The methods differ according to the time at which they are called up:
The method MB_DOCUMENT_BEFORE_UPDATE is called up before the FI document is created. This means that it is called up even if the program is terminated by an error during the subsequent processing. The update of data in separate tables should always be contained in function modules that are called up with the addition 'in update task'. This ensures that all the data is updated consistently.
The method MB_DOCUMENT_UPDATE is not carried out until update. This means that all updates are carried out immediately in their own tables and do not have to be contained in 'update task' in function modules. For performance reasons, you should not re-read the tables or carry out any time-consuming routines at this point.
You should always call up MB_DOCUMENT_BEFORE_UPDATE before MB_DOCUMENT_UPDATE, particularly if time is a critical factor when posting the material documents. The method MB_DOCUMENT_UPDATE is processed after the FI document numbers are called. As a result, no other FI documents can be posted until this document is completely updated.
Even if the two methods are in the same class, you cannot access the same global fields, as the methods are called up at different times and are therefore carried out in another roll area.
From the business add-in display, you can go to coding examples for both methods by choosing Goto -> Example coding -> Display
Note
The enhancement does not transfer any data to the material document, that is, you cannot change material document data before it is updated.
If this business add-in is not set up properly, it may result in an inconsistency between the documents and the stocks and between the material documents and the accounting documents. Inconsistencies like these may be caused by the following elements in the business add-in:
COMMIT WORK
Remote function call (CALL FUNCTION ... DESTINATION)
Own updates in document tables or stock tables (for example, update in tables MBEW, MARD, MSEG)
The unlocking of data (for example, via DEQUEUE_ALL)
Before the two business add-ins are called up, data is already flagged for the UPDATE. If a COMMIT WORK or a Remote Function Call is transmitted in the enhancement, these are written in the database. If another error occurs after the business add-ins are processed, you cannot carry out a complete ROLL BACK, as the data up to the COMMIT or Remote Function Call has already been written in the database. This can result in an inconsistent status (for example, material document without accounting document), which can only be repaired with considerable cost and effort.
The business add-ins are not suitable for customer-specific updates in the stock tables, as updates like these destroy the standard stock update.
Unlocking the data (for example, via DEQUEUE_ALL) is also critical, as the data that is to be updated is no longer protected from updates from external systems, and inconsistencies can result from parallel updates.
Before you activate an enhancement, check carefully that the business add-in does not contain any critical coding places.
If data inconsistencies have already occurred in your system as a result of the business add-in, remove the critical coding so that it does not cause any further inconsistencies.
Business Add-In: Change Item Data in Transaction MIGO
Use
Application component: MM-IM-GR-MIGO
The Business Add-In (BAdI) MB_MIGO_ITEM_BAdI enables you to set the storage location and item text in the transaction for goods movements ( MIGO).
The Business Add-In is called when a new item is inserted in MIGO or when an existing item is changed.
If changes are made at header-level, the Business Add-In does not run; the header data is then transferred to the external application for information.
All available header and item data is transferred from MIGO to the external application.
The determined storage location and item text of a material document item is transferred back from the external application.
Note
The Business Add-In is called in MIGO at different times. The external application must be prepared for this.
Standard settings
In the standard system, the Business Add-In is not active.
There is no default code that would run without an active implementation.
The Business Add-In is not filter-dependent.
The Business Add-In cannot be used more than once.
Activities
To activate the Business Add-In, you must create an active implementation. Do this in Inventory Management and Physical Inventory Customizing and choose the relevant activity under Maintain Customer-Exits and Business Add-Ins.
For more information about this procedure, see the SAP Library under
Basis Components -> ABAP Workbench -> Changing the SAP Standard -> Business Add-Ins -> Implementing Business Add-Ins.
Example
Storage location determination
The Business Add-In should be used for a customer-specific storage location determination.
Item text
Goods receipt for purchase order with account assignment: As the purchase order item does not have a material number, the material short text in the puchase order should be adopted as the item text.
Example of source text:
IF IS_GOITEM-MATNR IS INITIAL.
E_ITEM_TEXT = IS_GOITEM-MAKTX.
ENDIF.
If the material short text is to be adopted as the item text for all goods movements, the source text only consists of the following line:
Example of source text:
E_ITEM_TEXT = IS_GOITEM-MAKTX.
Further notes
Documentation on the BAdI method:
Change particular fields of a line (GOITEM)
ITEM_MODIFY
You can also call the documentation on the BAdI method via the menu, by carrying out the following steps:
1. Choose the tab page Interface.
2. Double-click on the relevant method.
3. Click on the right mouse button and choose Component documentation.
Change a Row from Certain Fields (GOITEM)
Functionality
The ITEM_MODIFY method makes it possible to set the storage location and item text in the transaction for goods movements ( MIGO).
The method is called if a new item is added in MIGO or if an existing item is changed.
If changes are made to the header, the method will not run; however, the header data is transferred to the external application for information.
All available header and item data is transferred from MIGO to the external application.
The external application then transfers back the determined storage location and the item text of a material document item.
Requirements
Note that the Business Add-In can run several times for each material document item if entries are changed on the entry screen, or if error messages are outputted.
Result
The storage location and item text is returned from the external application to MIGO. The item text is also saved in the accounting document.
Note:
Data is only copied into MIGO, if the corresponding fields are visible and ready for input.
Parameters
The following structures are transferred:
IS_GOHEAD: contains the header data for the goods movement
IS_GOITEM: contains the itemd ata for the goods movement
E_STGE_LOC: storage location
E_ITEM_TEXT: item text
Exceptions
None
Notes
GOITEM includes all information on an item, in other words, both business data (material number) and technical data (for example, whether or not a tab page is to be shown for an item). We recommend you only analyze the business data of an item, as the technical data may be changed due to new developments at SAP.
Documentation for Business Add-In:
BAdI in MIGO for Changing Item Data (MB_MIGO_ITEM_BADI)
<b>Also try out the BADI - MB_MIGO_BADI</b>
Business Add-In: Maintain External Detail Subscreens for Transaction MIGO
Use
Application component: MM-IM-GR; MM-IM-GI
With the Business Add-In (BAdI) MB_MIGO_BADI, you can extend the interface of the goods movements transaction ( MIGO) with additional tabstrip controls for the detailed information (detail tabstrips) and header information (header tabstrips). It is possible for an external application
to display an additional detail tabstrip with own subscreen (max. 10 lines) in MIGO
to display an additional header tabstrip with own subscreen (max. 3 lines) in MIGO
The program name, screen number and tab page text can be determined dynamically. Different screens can therefore be controlled according to the mode (for example, change mode, display mode, goods receipt, goods issue).
Pushbuttons
It is not possible to implement pushbuttons in the MIGO menu, but you can, however, implement pushbuttons directly on the external subscreen. The OK code from MIGO is forwarded to the external application so it can react.
Cursor Control
So that the cursor stays on the same subscreen after you press Continue, if it was positioned there before, the external application in the own PAI must hold the cursor positioning (on the same screen 'yes'/'no'; if 'yes', on which field), to set the cursor in PBO again.
Requirements
If you use the BAdI MB_MIGO_BADI in MIGO to update customer-own data, in addition to the material document, to the database, you should note the following:
The BAdI MB_MIGO_BADI is only active in transaction MIGO.
If you post goods movements with other transactions (for example, with MB01, MB1C, VL02N), you must ensure that customer data is also updated, if necessary.
You can do this by using the BAdI MB_DOCUMENT_BADI (Creating a material document) to post the goods movements with the transactions mentioned above.
Note that otherwise, posting the goods movements will lead to inconsistencies between SAP system data (for example, in stocks, material documents, FI documents) and customer data.
To avoid these inconsistencies, we recommend posting all goods movements with transaction MIGO.
Standard settings
In the standard system, the Business Add-In is not active.
There is no default code.
The Business Add-In is not filter-dependent.
The Business Add-In can be used more than once.
Activities
To activate the Business Add-In, you must create an active implementation. Do this in Inventory Management and Physical Inventory Customizing and choose the relevant activity under Maintain Customer-Exits and Business Add-Ins.
For more information about this procedure, see the SAP Library under
Basis Components -> ABAP Workbench -> Changing the SAP Standard -> Business Add-Ins -> Implementing Business Add-Ins.
Note that the Business Add-In can be used multiple times and therefore all active implementations are called and run through.
Create Implementations
BAdI definition MB_MIGO_BADI was created with transaction SE18.
Using transaction SE19, you can create an implementation for this BAdI. You can provide the methods with customer-defined code.
The BAdI definition can be used several times. In MIGO, five additional tabstrip control were defined for the detail screen, and five additional tabstrip controls for the header information. In other words, up to five different implementations can be created.
Recommendation
We recommend that you do not install the external application data directly in the implementation, but enclose it in function modules. You assign the screen with the subscreens to the corresponding function group; see the example implementation.
Example
For easier comprehension, an example code has been created for the BAdI MB_MIGO_BADI. The example implementation class isCL_EXM_IM_MB_MIGO_BADI.
To activate the example implementation, use transaction SE19 to create a new implementation and then activate it. Copy the example code with Goto -> Sample Code -> Copy.
The tabstrip controls MIGO BAdI Example are then displayed in MIGO for the header and detail information.
On the tabstrip control for the detail information, you can enter an additional quantity (and unit of measure). Both are saved in table MIGO_BADI_EXAMPL.
The text field SGTXT can also be changed. An example shows how an external application can change the data from the GOITEM (item data in MIGO) structure.
On the tabstrip control for the header information, you can enter an additional number. This is saved in table MIGO_BADI_EXAMP2.
Further notes
Documentation for BAdI methods:
Initialization and registration of external detail screens:
INIT
PBO of detail screen
PBO_DETAIL
PAI of detail screen
PAI_DETAIL
Insert / change line (GOITEM)
LINE_MODIFY
Delete line (GOITEM)
LINE_DELETE
MIGO reset (delete all internal data)
RESET
Post a goods movement
POST_DOCUMENT
Check item data for goods movement
CHECK_ITEM
Mode of transaction MIGO (action, reference document, etc.)
MODE_SET
Status information and header data
STATUS_AND_HEADER
Save held data
HOLD_DATA_SAVE
Load held data
HOLD_DATA_LOAD
Delete held data
HOLD_DATA_DELETE
PBO of header screen
PBO_HEADER
PAI of header screen
PAI_HEADER
Check item data for goods movement
CHECK_HEADER
You can also call the documentation on the BAdI method via the menu, by carrying out the following steps:
1. Choose the tab page Interface.
2. Double-click on the relevant method.
3. Click on the right mouse button and choose Component documentation.
Hope this will help.
Please reward suitable points.
Regards
- Atul

BADI ME_PROCESS_PO_CUST is not triggering while creating/changing PO

Hi,
I am new to BADIs,
I am trying to implement BADI ME_PROCESS_PO_CUST in ECC 6.0. I have done the implementation and activated. I kept a break point in PROCESS_ITEM method, but the BADI is not triggering while creating or changing the PO. Please advice me what could be the reason behind this?
I used the SQL trace but i couldn't get the BADI ME_PROCESS_PO_CUST in the list.
thanks in advance
Regards
Jagadish

hello jagdish,
implement this user exit.....
MM06E005...
go to EXIT_SAPMM06E_017 in that then you can put a break point in the user defined function module.....
or use
BREAK 'C5133392' (use your user in place of C5133392)....it will stop here while creating PO or changing PO...
now you can do whatever you want to do in create or change PO using this function exit......
perform the validations on import parameters.....to create or change ....and activate the project....
hope this will give you some idea and help

Client proxy message strucked in ECC queues

Hi All,
I am working on Proxy interface. My interface is like below
ECC 6----
>PI (7.1) -
>File
I had done the entire configuration in ECC and PI for proxy activation. While testing the interface in ECC system messages processed successfully, but the message strucked in queues (SMQ2) in ECC system. If run the queue manually the message processed successfully to the PI.
Can you please tell any more configurations required?
Regards,
Ramesh

Hi,
The queue used for Proxy call is not registerd in ECC system. You need to register the queue to process successfully.
you will get the name of Queue from SMQ2 t-code and register it with t-code SMQR.
Thanks
Swarup
Edited by: Swarup Sawant on Aug 24, 2009 8:03 AM

Workflow WS00000038 Purch.Req - Event REJECTED not triggered

Hi Friends!
(SAP ECC 6.0)
(Tcode SWE3 - BUS2009-REJECTED is active)
When using WS00000038 Purchase requisition we have problem when an item is REJECTED.
the Event that is triggered is BUS2009-SIGNIFICANTLYCHANGED. This leads to that the Workflow end up with status COMPLETED and NO further handling of the actual Rejection that were made.
IF BUS2009-REJECTED were triggered instead, then WS00000038 would have followed another path in the workflow which is to handle the REJECTION via another TASK.
Why is BUS2009-REJECTED not triggered when button "REJECT" Requisition is pressed (ME54N).
Best regards
Henrik

In this aproval step within WS00000038 it is actually ME54N that is called.
The result in the task of the workflow is an EXTERNAL EVENT that is triggered.
In my case it is BUS2009-SIGNIFICANTLYCHANGED that is triggered instead of BUS2009-REJECTED.
this is what causes my Workflow WS00000038 to choose the wrong path.
Does anyone have a solution of how to get BUS2009-REJECTED triggered via ME54N when I actually press button to REJECT and then SAVE.
Best reg
Henrik

End_of_page is not triggering in ALV

hi mates
         the code below is not triggering end-of-page event, can anyone help me. reply asap
TABLES:VBAP.
TYPE-POOLS:SLIS.
DATA: BEGIN OF VBAP_TYPE OCCURS 0,
      VBELN TYPE VBAP-VBELN,
      POSNR TYPE VBAP-POSNR,
      MATKL TYPE VBAP-MATKL,
      MATNR TYPE VBAP-MATNR,
      END OF VBAP_TYPE.
DATA:GET_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV,
     WA_FIELDCAT TYPE SLIS_FIELDCAT_ALV,
     HT_EVENT    TYPE SLIS_T_EVENT,
     WA_EVENT     TYPE SLIS_ALV_EVENT,
     HT_HEADER   TYPE SLIS_T_LISTHEADER,
     WA_HEADER   TYPE SLIS_LISTHEADER.
START-OF-SELECTION.
PERFORM GET_DATA.
PERFORM GET_FIELDCATALOG.
PERFORM FIELD_EVENT.
PERFORM FIELD_DISPLAY.
*&      Form get_data
      text
FORM GET_DATA.
SELECT VBELN
         POSNR
         MATKL
         MATNR
       FROM VBAP
       INTO TABLE VBAP_TYPE.
ENDFORM.                    "get_data
*&      Form get_fieldcatalog
      text
FORM GET_FIELDCATALOG.
CLEAR WA_FIELDCAT.
WA_FIELDCAT-COL_POS = 1.
WA_FIELDCAT-FIELDNAME = 'VBELN'.
WA_FIELDCAT-SELTEXT_L = 'sales doc'.
APPEND WA_FIELDCAT TO GET_FIELDCAT.
CLEAR WA_FIELDCAT.
clear wa_fieldcat.
wa_fieldcat-col_pos = 1.
wa_fieldcat-fieldname = 'VBELN'.
wa_fieldcat-seltext_l = 'sales doc'.
append wa_fieldcat to get_fieldcat.
clear wa_fieldcat.
WA_FIELDCAT-COL_POS = 2.
WA_FIELDCAT-FIELDNAME = 'POSNR'.
WA_FIELDCAT-SELTEXT_L = 'sales doc item'.
APPEND WA_FIELDCAT TO GET_FIELDCAT.
CLEAR WA_FIELDCAT.
WA_FIELDCAT-COL_POS = 3.
WA_FIELDCAT-FIELDNAME = 'MATKL'.
WA_FIELDCAT-SELTEXT_L = 'Material Group'.
APPEND WA_FIELDCAT TO GET_FIELDCAT.
CLEAR WA_FIELDCAT.
WA_FIELDCAT-COL_POS = 4.
WA_FIELDCAT-FIELDNAME = 'MATNR'.
WA_FIELDCAT-SELTEXT_L = 'Material No'.
APPEND WA_FIELDCAT TO GET_FIELDCAT.
CLEAR WA_FIELDCAT.
ENDFORM.                    "get_fieldcatalog
*&      Form field_display
      text
FORM FIELD_DISPLAY.
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
EXPORTING
   I_INTERFACE_CHECK              = ' '
   I_BYPASSING_BUFFER             =
   I_BUFFER_ACTIVE                = ' '
      I_CALLBACK_PROGRAM             = SY-CPROG
   I_CALLBACK_PF_STATUS_SET       = ' '
   I_CALLBACK_USER_COMMAND        = ' '
   I_STRUCTURE_NAME               =
   IS_LAYOUT                      =
      IT_FIELDCAT                    = GET_FIELDCAT[]
   IT_EXCLUDING                   =
   IT_SPECIAL_GROUPS              =
   IT_SORT                        =
   IT_FILTER                      =
   IS_SEL_HIDE                    =
   I_DEFAULT                      = 'X'
   I_SAVE                         = ' '
   IS_VARIANT                     =
      IT_EVENTS                      = HT_EVENT
   IT_EVENT_EXIT                  =
   IS_PRINT                       =
   IS_REPREP_ID                   =
   I_SCREEN_START_COLUMN          = 0
   I_SCREEN_START_LINE            = 0
   I_SCREEN_END_COLUMN            = 0
   I_SCREEN_END_LINE              = 0
   IR_SALV_LIST_ADAPTER           =
   IT_EXCEPT_QINFO                =
   I_SUPPRESS_EMPTY_DATA          = ABAP_FALSE
IMPORTING
   E_EXIT_CAUSED_BY_CALLER        =
   ES_EXIT_CAUSED_BY_USER         =
    TABLES
      T_OUTTAB                       = VBAP_TYPE
   EXCEPTIONS
     PROGRAM_ERROR                  = 1
     OTHERS                         = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    "field_display
*&      Form field_event
      text
FORM FIELD_EVENT.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
EXPORTING
   I_LIST_TYPE           = 0
   IMPORTING
     ET_EVENTS             = HT_EVENT.
WA_EVENT-NAME = SLIS_EV_TOP_OF_PAGE .
WA_EVENT-FORM = 'TOP_OF_PAGE'.
APPEND WA_EVENT TO HT_EVENT.
CLEAR WA_EVENT.
WA_EVENT-NAME = SLIS_EV_END_OF_PAGE .
WA_EVENT-FORM = 'END_OF_PAGE'.
APPEND WA_EVENT TO HT_EVENT.
CLEAR WA_EVENT.
READ TABLE ht_event INTO wa_event
                     WITH KEY name = slis_ev_top_of_page .
EXCEPTIONS
   LIST_TYPE_WRONG       = 1
   OTHERS                = 2
IF sy-subrc = 0.
   wa_event-form = 'TOP-OF-PAGE'.
   wa_event-form = 'END_OF_PAGE'.
   MODIFY ht_event FROM wa_event INDEX sy-tabix.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    "field_event
*&      Form top_of_page
      text
FORM TOP_OF_PAGE.
CLEAR WA_HEADER.
WA_HEADER-TYP = 'H'.
WA_HEADER-INFO = ' this is the sales document data'.
APPEND WA_HEADER TO HT_HEADER.
CLEAR WA_HEADER.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
      IT_LIST_COMMENTARY       = HT_HEADER
I_LOGO                   =
I_END_OF_LIST_GRID       =
I_ALV_FORM               =
ENDFORM.                    "top_of_page
*&      Form END_OF_Page
      text
FORM END_OF_PAGE.
WA_HEADER-TYP = 'H'.
WA_HEADER-INFO = ' this is the end of page'.
APPEND WA_HEADER TO HT_HEADER.
CLEAR WA_HEADER.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
    IT_LIST_COMMENTARY       = HT_HEADER
I_LOGO                   =
I_END_OF_LIST_GRID       =
I_ALV_FORM               =
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
     it_list_commentary       = ht_header
I_LOGO                   =
I_END_OF_LIST_GRID       =
I_ALV_FORM               =
endform.

Hi,
Try this code for end_of_page is not triggering in ALV
TYPE-POOLS : slis.
TABLES : mara,
         makt,
         marc.
DATA : BEGIN OF itab OCCURS 0,
        matnr LIKE mara-matnr,
        maktx LIKE makt-maktx,
        werks LIKE marc-werks,
       END OF itab.
DATA : t_fcat TYPE slis_t_fieldcat_alv,
       t_eve TYPE slis_t_event,
       st_line TYPE slis_listheader,
       t_list_top_page TYPE slis_t_listheader,
       t_list_end_page TYPE slis_t_listheader.
DATA : t_mat LIKE mara-matnr.
SELECTION-SCREEN : BEGIN OF BLOCK blk1 WITH FRAME TITLE text-001.
SELECT-OPTIONS : mat FOR mara-matnr.
SELECTION-SCREEN : END OF BLOCK blk1.
INITIALIZATION.
PERFORM build_cat USING t_fcat.
PERFORM build_eve.
START-OF-SELECTION.
PERFORM get_data.
PERFORM build_header USING t_list_top_page[].
PERFORM build_footer USING t_list_end_page[].
PERFORM dis_data.
*&      Form buils_cat
      text
     -->TEMP_FCAT text
FORM build_cat USING temp_fcat TYPE slis_t_fieldcat_alv.
DATA : wa_fcat TYPE slis_fieldcat_alv.
wa_fcat-tabname = 'ITAB'.
wa_fcat-fieldname = 'MATNR'.
wa_fcat-seltext_m = 'Material'.
APPEND wa_fcat TO temp_fcat.
CLEAR wa_fcat.
wa_fcat-tabname = 'ITAB'.
wa_fcat-fieldname = 'MAKTX'.
wa_fcat-seltext_m = 'Material Description'.
APPEND wa_fcat TO temp_fcat.
CLEAR wa_fcat.
wa_fcat-tabname = 'ITAB'.
wa_fcat-fieldname = 'WERKS'.
wa_fcat-seltext_m = 'Plant'.
wa_fcat-row_pos = 2.
APPEND wa_fcat TO temp_fcat.
CLEAR wa_fcat.
ENDFORM.                    "build_cat
*&      Form build_eve
      text
FORM build_eve.
DATA : wa_eve TYPE slis_alv_event.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
   EXPORTING
     i_list_type           = 0
   IMPORTING
     et_events             = t_eve
EXCEPTIONS
LIST_TYPE_WRONG       = 1
OTHERS                = 2
IF sy-subrc 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
READ TABLE t_eve INTO wa_eve WITH KEY name = 'END_OF_LIST'.
IF sy-subrc = 0.
    wa_eve-form = 'END_OF_PAGE'.
    MODIFY t_eve FROM wa_eve INDEX sy-tabix.
ENDIF.
ENDFORM.                    "build_eve
*&      Form get_data
      text
FORM get_data.
SELECT maramatnr maktmaktx marc~werks INTO CORRESPONDING FIELDS OF TABLE itab
FROM mara INNER JOIN makt ON
maramatnr = maktmatnr
INNER JOIN marc ON
maramatnr = marcmatnr
WHERE mara~matnr IN mat.
ENDFORM.                    "get_data
*&      Form dis_data
      text
FORM dis_data.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
   EXPORTING
     i_callback_program                = 'ZALV_PRDS'
     i_callback_top_of_page            = 'TOP_OF_PAGE'
     it_fieldcat                       = t_fcat
     i_save                            = 'A'
     it_events                         = t_eve
   TABLES
      t_outtab                          = itab
EXCEPTIONS
PROGRAM_ERROR                     = 1
OTHERS                            = 2
IF sy-subrc 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    "dis_data
*&      Form build_header
      text
     -->TEMP_LIST          text
     -->TTYPE              text
     -->SLIS_T_LISTHEADER text
FORM build_header USING temp_list TYPE slis_t_listheader.
CLEAR st_line.
st_line-typ = 'H'.
st_line-info = 'Material Info'.
APPEND st_line TO temp_list.
ENDFORM.                    "build_header
*&      Form build_footer
      text
     -->TEMP_LIST text
FORM build_footer USING temp_list TYPE slis_t_listheader.
CLEAR st_line.
st_line-typ = 'H'.
st_line-info = 'Dhwani Shah'.
APPEND st_line TO temp_list.
ENDFORM.                    "build_header
*&      Form top_Of_page
      text
FORM top_of_page.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
      it_list_commentary = t_list_top_page.
ENDFORM.                    "top_Of_page
*&      Form end_of_page
      text
FORM end_of_page.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
      it_list_commentary = t_list_end_page.
ENDFORM.                    "end_of_page
Reward Points if usefull
Regards
Fareedas

Proxy not Triggered on ECC

Similar Messages

Maybe you are looking for