Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Restrict PO output during PO Change

Former Member
0 Kudos
1,266


Hello

I want to restrict PO output during PO change based on some fields. In case if any changes are done in these fields than PO output should not trigger else PO output should be triggered.

How do we restrict PO output based on some fields?

Thanks,

Shravan

6 REPLIES 6

joydeep_mukherjee2
Active Participant
0 Kudos
465

Dear sir ;

I think its not possible in standard .The routine will be your routine by which you can trigger the o/p .

Joydeep

0 Kudos
465

Hi Joydeep,

Thanks for the reply.

Yes this is not possible as per standard SAP. A routine needs to be assigned to the output and write the code in the routine to restrict. But in the routine how do we find in which fields, PO is being changed?

Shravan

joydeep_mukherjee2
Active Participant
0 Kudos
465

Dear sir ;

you can identify PO changes in CDPOS and CDHDR table .

you need to define the kind of change that will restrict to triggering of second output .

Joydeep Mukherjee

Former Member
0 Kudos
465

Hi,

As Joydeep Mukherjee wrote if you identify some changes in your restricted files you can use the following FM to block the PO and not allow any action on it.

You can do it using the FM´s:

ENQUEUE_EMEKKOS   --> Block the object  (PO)

This oder one is just to unblock the block

DEQUEUE_EMEKKOS  --> Deblock the object (PO)

Regards

Luis

Former Member
0 Kudos
465

Hi,

Check if the print program is custom. Are you using standard output type or custom message type?

Depend on it we can restrict to trigger PO changes.

Regards,

Pravin

Former Member
0 Kudos
465

I am using custom output type and custom program but I don't want to restrict this in the output type driver program.

I want to restrict this at routine level so that output type will not trigger at all during PO change.

We can read CDHDR and CDPOS only once the PO is committed to database. By the time routine triggers PO will not be committed to database yet.