Skip to Content
0
Dec 11, 2006 at 07:04 PM

Services For Object & Call Transaction using BDCDATA

104 Views

Hi All,

I am having an issue with the CALL TRANSACTION functionality.

Let me give you the full background.

We have extended the EBAN table to include a field called ZZPRIORITY. We need to give visibility into this field from the ME57 transaction, so that buyers will know if there are any high priority purchase requisitions outstanding. Rather than doing a modification to ME57, I have written a small report which will tell the user how many high-priority and low-priority purchase requisitions he/she has outstanding.

From this report, the user clicks a line and the report goes to ME57 with the appropriate selection criteria. I have done this using a CALL TRANSACTION USING bdcdata. (using SUBMIT is not a viable option - Call Transaction/Submit issues with ME57)

So the basic flow is -

1) User calls transaction ZME57

2) User clicks on Priority Purchase Requests

3) User is taken to the ME57 list of outstanding requisitions.

4) User double clicks a requisition and is taken to ME52N to process the requisition.

Here is my problem. When I use my custom transaction (ZME57) to get to the purchase request, the menu path "Services For Object" is greyed out once you reach ME52N. If you use the standard tcode (ME57), that menu path is not greyed out once you reach ME52N.

I have tried including the OPTIONS FROM ctu_params and specifying:

ctu_params-nobiend = 'X'.

But that doesn't seem to help. The only way I can seem to get that menu path to be available is if I CALL TRANSACTION without using the bdcdata table.

Is there any way around this?

Thanks