Blocking Purchase Requisition

Dear Experts,
There is a way to prevent the change of a Purchase Requisition if there is already a Purchase Order created with reference to that PR?
Please help.
Javier Sandoval Vera
Ecuador

Hello,
You should be able to validate PO Create status in method PROCESS_ITEM using BADI ME_PROCESS_REQ_CUST and throw message accordingly.
Thanks,
Venu

Similar Messages

Need reasons for blocking Purchase requisition and service entry sheet.

Hi All,
I need reasons for blocking service entry sheet and purchase requisition.
Also want the reasons for reversing the approval of service entry sheet.
Its urgent ......

Hi Nilesh,
It is not possible to block a service entry sheet as such. You could only revoke a service entry sheet. Some of the possible reasons are, you are not satisfied with the quality of service provided by the vendor. Or it could also be due to change in the services to be performed or it could even be as simple as erronous entry of services in the entry sheet.
However from ERP 2005, it should be possible to return the services by marking the returns indicator.In case of materials, it is possible to put a materials PO on hold. But in case of services, the hold option does not arise as a service cannot be performed/completed till all the approvals are received.
Hope this answer helps you.

Block purchase requisition after purchase order created

Hi,
We have the requirement that users cannot modify a PR after a PO has been created.
Do you know if there is a standar message or someway to do it?
Some message similar as 06 648 but not only for quantity.
Thanks in advanced

hi..
System can be configured in such a way that after PO creation with reference to PR, user will not be able to change the PR Quantity. In this case system will issue an error Message no. 06608 saying that Requisition already converted into purchase order
This will be done under path: - SPRO > MM > Purchasing > Environment Data > Define Attributes of System Messages > System messages
hope it works..
Thanks

Purchase requisition from sales document' not possible due to a credit bloc

hi experts,
i have to confirm delivery date and quantity for some purchase order items but i'm not able because i receive following message:
Subsequent function 'Purchase requisition from sales document' not possible due to a credit block'
Purchase requisition belongs to a sales order which has customer 10000.
The customer 10000 was block from FD32 but now i have unblock the customer from FD32, i have assigned customer to a category risk which is only a warning. (in OVA8 risk category 002 static check, reaction C, status/block uncheck )
There is any possiblilities to confirm quantity ?? I mean ... i understand that sales order was created when the customer was block due to credit limit exceded ... but now the customer is not blocked.
What should i do?
Thank you.

Hi Dan
If you want to confirm the delivery date then change the static check reaction to B . in OVA8 . But if you change the static check reaction to A , you can do Delivery and billing also
Regards
Srinath

Blocking a Requisition Line Item if A Purchase order exists

Hi All,
We are looking at a way to block a purchase requisition (not allow the end user to make changes) if a Purchase Order Exists for that purchase requisition line item. Is there a way of doing this without having to use a user exit?
We do have release strategies on requisitions so we can control the filed status there but this is not really going to solve the 'problem'
Your help will appreciated.
Kind Regards,
GA

Hi,
Thanks for your help. The end user are mostly changing the value, quantity and adding specification in the text fields. But the procurement department do not pick these changes up as the PO is already with the Vendor.
Regards,
GA

Purchase requisition with reference to blocked sales order

Hello,
we are creating purchase requisitions (PR) manually with reference to a sales order (account assignment Z). When this sales order is blocked, we still can issue the purchase requistion.
What can we do to avoid this? I think in 2 solutions:
- use enhancement MEREQ001 to show error message when SO is blocked, so PR is not created. Is this possible?
- create a release strategy for PR created in that plant (tr. OME6). The problem is that release strategy refers to an amount in the PO, and not to other factor, like SO blocked. Maybe in the former enhancement we can set the field EBAN-GSFRG to 'X'?
Thanks for your help.

Many thanks for your answer. It help me to solve the issue.
So applying note 738171, with transaction OVB5 (or VOFM, requirements->subsequent functions->Purch.requisitions) we create one new requirement, ie RV07A900, and then we apply the rule that if we have delivery or billing block, that is, VBAK-LIFSK or VBAK-FAKSK not empty, then we set an error with a code similar to this:
            da_sy-msgid = 'Z1'.    (message class)
            da_sy-msgno = '001'. (message number)
            error_exception = true.
and then the PR is not created.
Regards.

Block Plan Order and Purchase Requisition in Sales order creation.

Please tell me, how to block Plan Order and Purchase Requisition while creating Sales Order. When we create a sales order, plan order and purchase requisitions are also created by their own, please tell me, how can we block them while creating sales order. Please do let me know as soon as possible.

hi,
generally thy wil not be created automatically.
may be som configuration or exit is used in ur system.
check in debugging mode while saving ur salesorder.

Block item in the purchase requisition

Hi expert,
do you know some bapi to modify a purchase requisition item ?
p.s. The modify consist to block only some item.
tks a lot,
bye.

Hi Frank,
tks for your reply, anyway I asked about some bapi ... not batch input and not transaction me52 .
bye.

Item Purchase Requisition Block

For cash-relevant sales order line items that are assigned a u201Cdirect from vendoru201D item category and the deposit paid < 100% of the total line item value, then automatically set the purchase requisition block should be applied.
For the above case I am blocking item by setting user status as 'UPRq'(For blocking PR) in the item status tab, For that I am using FM status_update. This code is handled in one User exit.
after the above user exit, the standard prog will again assigning the 'URel'(User release). the result in the item status is UPRq and URel.Means both values are active. I want one user status active and other will be inactive.
<<Text removed by moderator>>
Edited by: Matt on Nov 18, 2008 1:59 PM

solved by job

Without crating purchase requisition ,shall we block/hold some budget agai

Hi All,
Is there a way that without crating purchase requisition ,shall we block/hold some budget against a wbs. also we are using project level budgeting .for example I want to commit 100 budget without creating any PR/PO. Please suggest.
With Thanks/Regards,
Vivek
Edited by: vivek tripathi on Mar 5, 2012 3:05 PM

Hello Vivek,
Gokul is correct, commitment is contributed to assigned value in CJ30. PR/PO process always increase the assigned value. This is standard SAP system. You have an option to deactivate the PR process in updating the assigned value. SAP note 1307755 could be applied.
You may use ''save as completed' function in transaction MIR7, this is park process and commit to assigned value (see SAP note 178837) but this is involving PO process.
Regards, Gordon

Block ID in Purchase Requisition

Dear All,
Is there any possibility to create a new Block ID for Purchase Requisition? How and where to configure?
Thanks in Advance,
Regards,
S.Suresh

Hi,
I'm Trying to add a new value in Block ID Field (Status TAB, ME52N TX).
In the domain BLCKD I add a Fixed Value Append with the new option I need (3 Bloqueada por comprador).
In the ME52N TX the new value appears ok, but doesn't work fine. If I select the new values all the Status tab fields (BlockID, Blkg Text, etc) convert into not editable. When I select a standard block id value the same fields appear as editable.
Anybody know how i can solved this problem?
Thanks in Advance,
Florencia.

Block Project Purchase Requisition using User Status

Dear All,
We need a copy of TECO, we tried to create a new status using BS22 transaction but its totally new activity of creating the system status. This transaction does not allow to copy an existing status. is there any other way to do so
We alos tried to block the Purchase Requisition using user status, but its not working. Please guide
Thanks in advance.
Murtaza

Yes, you are right I need the said status for WBS Element. I have assigned it to relevant WBS Elements but not working.
Let me explain the scenario little more, there are activities having commitments (Purchase Requisitions), we need to process the existing PRs but new commitments must be blocked. we need to use status on WBSE to control it so that if we need to re-open the new commitments, we can do it by disabling the status.
Murtaza

Purchase Requisition Is Being Getting Created In APO But not being publishe

On doing, SNP Location Heuristics on one of our item, purchase requisition is being getting created in APO (We are able to see the same in RRP3) but the same is not being getting published in ECC. On doing CCR of the said location - product combination, it is showing Error u201C182u201D. We have checked the following parameters :-
Item is an APO Item i.e. X0.
It is having a proper Purchasing Group.
As This be a purchase item. So, it is having a valid single Purchase Info Record.
Item Has Not Been Blocked At Any Level.
Vendor From Whom This Item is being getting procured is also open (Not Blocked).
Please suggest what else to be checked and what else can be the reason for non-flowing of purchase requisition from APO to ECC.
Thanks & Best Regards,
Sanjeev Chugh

Hi Sanjeev,
Please check change pointers if any and send them to ECC. Check the order in the planning book whether it has picked the same source for which there is a Purchase info record. If these all are fine then You send them to ECC from the CCR then check the log in ECC through CFG1 tcode.
Regards,
Kishore k Reddy

Release strategy for purchase requisition does not kick in

Hi Gurus!
I've been struggling with this issue for some weeks now.
I have set up the release strategy configuration for purchase requisitions with classifications.
However, if I create a purchase requisition the release functionality is not taken into account by the system.
See below some more information regarding my configuration:
1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
4. I have 5 release codes. Grp: T1, Code: 01....05
5. I have 2 release indicators:
"R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
"X = Blocked", Changeabil: 4, Value chgs. 100,0
6. I have 1 release strategy:
"T1 with Grp T1"
- one release group, 01 Manager
- release prerequisites not applicable because of only one release group
- release status, nothing marked = blocked, 01 marked = released
- classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
I intentionally kept the configuration as simple as possible so I can try to get it working first.
Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
Could you please assist in getting this working?

Hi,
Have you checked in CL30/CL30N if your release strategy is derived successfully?
See section 3 of Note 365604. A small section of it:
You can use transaction CL30 search for an object using the data
of the purchase requisition/purchase order. Here, it is important
that the object search determines exactly one strategy. If this
is not the case, this indicates that there are overlapping
strategies in the system or that the release strategies in
Customizing do not correspond with those from transaction CL24.
See the previous point. If the object search returns more than
one result, the system subsequently determines an incorrect
release strategy or no release strategy at all.
If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
The following assignment statement has to exist within activated SAP
enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
for purchase requisitions:
E_CEBAN = I_CEBAN.
Regards,
Purnima.

Generated a report which gives PR(Purchase Requisition) analysis using ALV.

hi experts,
please give me tables and fields for following report, and also exlain me briefly,
Generated a report which gives PR(Purchase Requisition) analysis using ALV.
thanks in advance,
radhakrishna

Hi
please find this report which link SO PO PR and Prd Ord and there status.
>
REPORT z_so_info.
TABLES: vbak, vbap, afko, afpo.
*Field catalog
TYPE-POOLS: slis.
DATA: lv_repid TYPE sy-repid VALUE sy-repid,
xfield TYPE slis_t_fieldcat_alv,
afield TYPE slis_fieldcat_alv.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 1(25) text-002.
SELECT-OPTIONS: so_so FOR vbak-vbeln OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE text-003.
PARAMETERS:
p_kunnr LIKE vbak-kunnr, " sold-to
p_kunwe LIKE vbak-kunnr. " ship-to
SELECTION-SCREEN END OF BLOCK b2.
*Constants
CONSTANTS: c_zor TYPE vbak-auart VALUE 'ZOR',
c_we TYPE vbpa-parvw VALUE 'WE',
c_ag TYPE vbpa-parvw VALUE 'AG'.
c_space TYPE space.
*Ranges
RANGES: ra_parvw FOR vbpa-parvw,
ra_kunnr FOR vbpa-kunnr.
*Tables
DATA: BEGIN OF gt_output OCCURS 0,
vbeln LIKE vbak-vbeln, " sales order number
posnr LIKE vbap-posnr, " SO item number
matnr LIKE vbap-matnr, " material number
sh LIKE vbpa-kunnr, " Ship-to
sp LIKE vbpa-kunnr, " Sold-to
lifnr LIKE ekko-lifnr, " Vendor
bstnk LIKE vbak-bstnk, " PO number
banfn LIKE vbep-banfn, " Purchase requi
po_st TYPE char30, " PO status text
pstyv TYPE vbap-pstyv, " Item catagory
aufnr LIKE afpo-aufnr, " Production Order
prd_stat TYPE string, " Prd order status
END OF gt_output.
DATA: wa_output LIKE gt_output.
FIELD-SYMBOLS: <fs_output> LIKE gt_output.
*Table for sales order and PO
TYPES : BEGIN OF gs_data,
vbeln TYPE vbak-vbeln,
posnr TYPE vbap-posnr,
pstyv TYPE vbap-pstyv,
matnr TYPE vbap-matnr,
END OF gs_data.
DATA: gt_data TYPE STANDARD TABLE OF gs_data,
wa_data TYPE gs_data.
*Table for Production Orders
TYPES: BEGIN OF gs_prd,
aufnr TYPE afpo-aufnr,
posnr TYPE afpo-posnr,
kdauf TYPE afpo-kdauf,
kdpos TYPE afpo-kdpos,
wepos TYPE afpo-wepos, "Goods Receipt Indicator
elikz TYPE afpo-elikz, "Delivery Completed Indicator
objnr TYPE aufk-objnr, "Object number
getri TYPE afko-getri, "Confirmed Order Finish Date
gltri TYPE afko-gltri, "Actual finish date
END OF gs_prd.
DATA: gt_prd TYPE STANDARD TABLE OF gs_prd,
wa_prd TYPE gs_prd.
*Table for partner data
TYPES: BEGIN OF gs_partner,
vbeln TYPE vbak-vbeln,
posnr TYPE vbap-posnr,
parvw TYPE vbpa-parvw,
kunnr TYPE vbpa-kunnr,
END OF gs_partner.
DATA: gt_partner TYPE STANDARD TABLE OF gs_partner,
wa_partner TYPE gs_partner.
TYPES: BEGIN OF gs_po,
ebeln TYPE ekkn-ebeln,
ebelp TYPE ekkn-ebelp,
vbeln TYPE ekkn-vbeln,
vbelp TYPE ekkn-vbelp,
END OF gs_po.
DATA: gt_po TYPE STANDARD TABLE OF gs_po,
wa_po TYPE gs_po.
TYPES: BEGIN OF gs_preq,
vbeln TYPE vbep-vbeln,
posnr TYPE vbep-posnr,
banfn TYPE vbep-banfn,
END OF gs_preq.
DATA: gt_preq TYPE STANDARD TABLE OF gs_preq,
wa_preq TYPE gs_preq.
TYPES: BEGIN OF gs_po_stat,
ebeln TYPE ekko-ebeln,
procstat TYPE ekko-procstat,
lifnr TYPE ekko-lifnr,
END OF gs_po_stat.
DATA: gt_po_stat TYPE STANDARD TABLE OF gs_po_stat,
wa_po_stat TYPE gs_po_stat.
*Field symbols
FIELD-SYMBOLS: <fs> TYPE tj02t-txt04,
<fs_temp> TYPE tj02t-txt04,
<fs_stat> TYPE char30.
START-OF-SELECTION.
PERFORM fr_build_range.
PERFORM fr_get_data.
PERFORM fr_build_fc.
PERFORM fr_output.
*& Form fr_get_data
text
--> p1 text
<-- p2 text
FORM fr_get_data.
*Get SO
SELECT avbeln aposnr apstyv amatnr
FROM vbap AS a
JOIN vbak AS b
ON avbeln = bvbeln
JOIN vbpa AS c
ON bvbeln = cvbeln
INTO TABLE gt_data
WHERE b~vbeln IN so_so
AND b~auart EQ c_zor "Only Sales Orders
AND c~kunnr IN ra_kunnr. "from selection screen
DELETE ADJACENT DUPLICATES FROM gt_data COMPARING vbeln posnr.
*get data of the production order
IF NOT gt_data[] IS INITIAL.
SELECT aaufnr aposnr akdauf akdpos awepos aelikz
b~objnr
FROM afpo AS a
JOIN aufk AS b
ON aaufnr = baufnr
INTO TABLE gt_prd
FOR ALL ENTRIES IN gt_data
WHERE a~kdauf EQ gt_data-vbeln
AND a~kdpos EQ gt_data-posnr.
ENDIF.
*Get partner data
IF NOT gt_data[] IS INITIAL.
SELECT vbeln posnr parvw kunnr
FROM vbpa
INTO TABLE gt_partner
FOR ALL ENTRIES IN gt_data
WHERE vbeln EQ gt_data-vbeln.
ENDIF.
*Get Purchase Order
IF NOT gt_data[] IS INITIAL.
SELECT ebeln ebelp vbeln vbelp
FROM ekkn
INTO TABLE gt_po
FOR ALL ENTRIES IN gt_data
WHERE vbeln EQ gt_data-vbeln
AND vbelp EQ gt_data-posnr.
SELECT vbeln posnr banfn
FROM vbep
INTO TABLE gt_preq
FOR ALL ENTRIES IN gt_data
WHERE vbeln EQ gt_data-vbeln
AND posnr EQ gt_data-posnr.
ENDIF.
IF NOT gt_po[] IS INITIAL.
SELECT aebeln aprocstat a~lifnr
FROM ekko AS a
JOIN ekpo AS b
ON aebeln = bebeln
INTO TABLE gt_po_stat
FOR ALL ENTRIES IN gt_po
WHERE b~ebeln EQ gt_po-ebeln
AND b~ebelp EQ gt_po-ebelp.
ENDIF.
*Move data to output table
LOOP AT gt_data INTO wa_data.
wa_output-vbeln = wa_data-vbeln.
wa_output-posnr = wa_data-posnr.
wa_output-pstyv = wa_data-pstyv.
wa_output-matnr = wa_data-matnr.
READ TABLE gt_po INTO wa_po WITH KEY vbeln = wa_data-vbeln
vbelp = wa_data-posnr.
IF sy-subrc EQ 0.
wa_output-bstnk = wa_po-ebeln.
READ TABLE gt_po_stat INTO wa_po_stat WITH KEY ebeln = wa_po-ebeln.
IF sy-subrc EQ 0.
wa_output-lifnr = wa_po_stat-lifnr.
CASE wa_po_stat-procstat.
WHEN '01'.
wa_output-po_st = 'Version in process'.
WHEN '02'.
wa_output-po_st = 'Active'.
WHEN '03'.
wa_output-po_st = 'In release'.
WHEN '04'.
wa_output-po_st = 'Partially released'.
WHEN '05'.
wa_output-po_st = 'Released Completely'.
WHEN '08'.
wa_output-po_st = 'Rejected'.
ENDCASE.
ENDIF. "inner read subrc
ENDIF. "outer read subrc
READ TABLE gt_preq INTO wa_preq WITH KEY vbeln = wa_data-vbeln
posnr = wa_data-posnr.
IF sy-subrc EQ 0.
wa_output-banfn = wa_preq-banfn.
ENDIF.
READ TABLE gt_prd INTO wa_prd WITH KEY kdauf = wa_data-vbeln
kdpos = wa_data-posnr.
IF sy-subrc EQ 0.
wa_output-aufnr = wa_prd-aufnr.
*get the purchase requisition for production order as well
SELECT SINGLE banfn
FROM ebkn
INTO wa_output-banfn
WHERE aufnr EQ wa_prd-aufnr.
*Get the status of the production order
PERFORM fr_get_prd_stat USING wa_prd-objnr
CHANGING wa_output-prd_stat.
ENDIF. " sy-subrc
READ TABLE gt_partner INTO wa_partner WITH KEY vbeln = wa_data-vbeln
parvw = c_we.
IF sy-subrc EQ 0.
wa_output-sh = wa_partner-kunnr.
ENDIF.
READ TABLE gt_partner INTO wa_partner WITH KEY vbeln = wa_data-vbeln
parvw = c_ag.
IF sy-subrc EQ 0.
wa_output-sp = wa_partner-kunnr.
ENDIF.
APPEND wa_output TO gt_output.
CLEAR: wa_data, wa_prd,wa_partner,wa_output.
ENDLOOP.
ENDFORM. " fr_get_data
*& Form fr_build_range
text
--> p1 text
<-- p2 text
FORM fr_build_range .
*Range for partner function
MOVE 'I' TO ra_parvw-sign.
MOVE 'EQ' TO ra_parvw-option.
MOVE 'SH' TO ra_parvw-low. " we
APPEND ra_parvw.
CLEAR ra_parvw.
MOVE 'I' TO ra_parvw-sign.
MOVE 'EQ' TO ra_parvw-option.
MOVE 'SP' TO ra_parvw-low. " ag
APPEND ra_parvw.
CLEAR ra_parvw.
*Range for ship-to and sold-to
MOVE 'I' TO ra_kunnr-sign.
MOVE 'EQ' TO ra_kunnr-option.
MOVE p_kunnr TO ra_kunnr-low.
APPEND ra_kunnr.
CLEAR ra_kunnr.
MOVE 'I' TO ra_kunnr-sign.
MOVE 'EQ' TO ra_kunnr-option.
MOVE p_kunwe TO ra_kunnr-low.
APPEND ra_kunnr.
CLEAR ra_kunnr.
ENDFORM. " fr_build_range
*& Form fr_build_fc
text
--> p1 text
<-- p2 text
FORM fr_build_fc .
sales order number
afield-fieldname = 'VBELN'.
afield-seltext_s = 'Sales #'.
afield-ref_tabname = 'VBAK'.
APPEND afield TO xfield. CLEAR afield.
sales ITEM number
afield-fieldname = 'POSNR'.
afield-seltext_s = 'Item #'.
afield-ref_tabname = 'VBAP'.
APPEND afield TO xfield. CLEAR afield.
Material Number
afield-fieldname = 'MATNR'.
afield-seltext_s = 'Material #'.
afield-ref_tabname = 'VBAP'.
afield-outputlen = 10.
APPEND afield TO xfield. CLEAR afield.
*Vendor Number
afield-fieldname = 'LIFNR'.
afield-seltext_s = 'Vendor Num.'.
afield-ref_tabname = 'EKKO'.
APPEND afield TO xfield. CLEAR afield.
ship-to-party
afield-fieldname = 'SH'.
afield-seltext_s = 'Ship-to'.
afield-ref_tabname = 'VBPA'.
APPEND afield TO xfield. CLEAR afield.
sold-to-party
afield-fieldname = 'SP'.
afield-seltext_s = 'Sold-to'.
afield-ref_tabname = 'VBPA'.
APPEND afield TO xfield. CLEAR afield.
*PO number
afield-fieldname = 'BSTNK'.
afield-seltext_s = 'PO NUM'.
afield-ref_tabname = 'EKKO'.
APPEND afield TO xfield. CLEAR afield.
*PO status
afield-fieldname = 'PO_STAT'.
afield-seltext_s = 'Step'.
afield-ref_tabname = 'zbacklog_v2'.
APPEND afield TO xfield. CLEAR afield.
*PO step status
afield-fieldname = 'PO_ST'.
afield-seltext_s = 'PO.Status'.
afield-ref_tabname = 'zbacklog_v2'.
APPEND afield TO xfield. CLEAR afield.
*Purchase requisition
afield-fieldname = 'BANFN'.
afield-seltext_s = 'Pur. Req.'.
afield-ref_tabname = 'VBEP'.
APPEND afield TO xfield. CLEAR afield.
*Item catagory
afield-fieldname = 'PSTYV'.
afield-seltext_s = 'Itm. Catg'.
afield-ref_tabname = 'VBAP'.
APPEND afield TO xfield. CLEAR afield.
*Prodcution Order number
afield-fieldname = 'AUFNR'.
afield-seltext_m = 'Prod.Order'.
afield-ref_tabname = 'AFKO'.
APPEND afield TO xfield. CLEAR afield.
*PRODCUTION status
afield-fieldname = 'PRD_STAT'.
afield-seltext_s = 'Prd. Step'.
afield-ref_tabname = 'zbacklog_v2'.
afield-outputlen = 20.
APPEND afield TO xfield. CLEAR afield.
*PRODUCTION step status
afield-fieldname = 'PRD_ST'.
afield-seltext_s = 'Prd. Status'.
afield-ref_tabname = 'zbacklog_v2'.
APPEND afield TO xfield. CLEAR afield.
ENDFORM. " fr_build_fc
*& Form fr_output
text
--> p1 text
<-- p2 text
FORM fr_output .
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
EXPORTING
i_callback_program = sy-repid
I_CALLBACK_PF_STATUS_SET = ' '
I_CALLBACK_USER_COMMAND = ' '
I_STRUCTURE_NAME =
IS_LAYOUT =
it_fieldcat = xfield[]
i_default = 'X'
i_save = 'A'
TABLES
t_outtab = gt_output
EXCEPTIONS
program_error = 1
OTHERS = 2.
ENDFORM. " fr_output
*& Form fr_get_prd_stat
text
-->P_WA_PRD_OBJNR text
FORM fr_get_prd_stat USING p_objnr CHANGING p_prd_stat.
DATA: lt_status TYPE STANDARD TABLE OF jstat,
wa_status TYPE jstat,
lv_status TYPE tj02t-txt04,
lv_temp2 TYPE char5,
lv_buff TYPE string.
CALL FUNCTION 'STATUS_READ'
EXPORTING
client = sy-mandt
objnr = p_objnr
only_active = 'X'
TABLES
status = lt_status
EXCEPTIONS
object_not_found = 1
OTHERS = 2.
LOOP AT lt_status INTO wa_status.
IF wa_status-stat(1) EQ 'I'.
SELECT txt04 FROM tj02t
INTO lv_status
WHERE istat EQ wa_status-stat
AND spras EQ 'E'.
ENDSELECT.
lv_temp2 = lv_status.
CONCATENATE lv_temp2 p_prd_stat INTO p_prd_stat
SEPARATED BY ','.
ENDIF.
CLEAR: wa_status, lv_status, lv_temp2.
ENDLOOP.
lv_buff = p_prd_stat.
*Status of Production Order
IF lv_buff CS 'CRTD'.
p_prd_stat = 'Not Active'.
ENDIF.
IF lv_buff CS 'REL'.
IF lv_buff CS 'GMPS'.
p_prd_stat = 'Printed In Prod'.
ELSE.
p_prd_stat = 'Printed'.
ENDIF.
ENDIF.
IF lv_buff CS 'TECO'.
p_prd_stat = 'Technically Compt.'.
ENDIF.
ENDFORM. " fr_get_prd_stat
>

Blocking Purchase Requisition

Similar Messages

Maybe you are looking for