Unchange the Block Reason in FB02/FB09

In the standard settings the payment block 'A' can be removed from a document using FB02/FB09 transaction. We want that user should not be able to change the Block 'A' from the document using FB02/FB09. In FB02/FB09, the payment block field should be greyed out. How can we do this ?

I changed the 'payment block' field in the document channge rules and the blocked invoice was found not changeable using FB02.
After that I executed MRBR transaction (release of blocked invoices) and released the blocked invoice for posting. But my current problem is that, when MRBR is done, it releases the entire invoice items i.e. there are certain items in the invoice which should not be paid to the vendor any time. If I do MRBR, it releases the retention items also, which should be prevented. How can I achieve this ?

Similar Messages

Unchanged the block Reason in FB02/FB09

In the standard settings the payment block "A" can be removed from a document using FB02/FB09 transaction. We want that user should not be able to change the block "A" from the document using FB02/FB09, the payment block field should be greyed out. How can we do this ?

in OB27 for your payment block key A, you need to select the appropriate check boxes and SAVE

Storing the Variance Block Reason Code in the Parked Invoice Document

Folks,
When I perform parking an incoming invoice (MIR7 or MIRO), system checks for price variance and issues the message. When I save the document, block reasons are not stored at Parked document level. Only when I post the document, the reason code 'R' is stored in the document.
Is there a way to get the Block reason in the parked document?
Thanks in advance. Murali

I am still researching this issue. Let me know if there are any options or ideas.
Thanks.

Custom invoice blocking reason

When posting an invoice, several checks are done to see whether invoice items should be blocked for payment. This is being done based on price and quantity. Right now we want to block payment for an incoming invoice item if that item does not have a corresponding PO item.
To this end we want to (ab)use the blocking reason for quality. When posting an invoice, there will be a time in the code that blocking reasons will be checked, at least for price and quantity. At that point we would like to insert our own code to set the quality block field if required.
Is there a way of customizing this process or creating an additional check without having to adjust standard SAP? Thanks in advance for the help!

An update and a question on the issue. The badi eventually didn't work for us, the additional checks it performed made it very hard to work with. What we did was adjust standard SAP in the routine for quality check. If our check returned negative, we set the quality block and return the process to SAP. Luckily this isn't a coding beauty contest, but it works perfectly.
Now we've been asked to implement the same process in another system. Newer system (SAP ECC 6.0), so once again we want to check whether there is a better way of solving the issue.
We know we're able to define custom blocking reasons. However they all seem to be related to tolerance level checking, which is not what we want to do.
Is there any way of creating a custom blocking reason on header or item level, which we can set with custom ABAP coding? Then we can program what we want to check and when to set the block.

Enhancement/Exit to flag Blocking Reason (RSEG-SPGRS) in MIRO

Hi,
I am facing a problem right now since I cannot find any exit/enhancements that can flag the Blocking Reason (RSEG-SPGRS) in transaction MIRO.
It is so much appreciated if you can help me to identify which exit/enhancement should I use.
Thank you in advance.

Hi,
This is what i´ve found out:
field RSEG-SPGRS is flagged within fm MR_BLOCKING_REASON_S.
And this field is flagged according to the criteria set in tables:
T169P (Parameters, Invoice Verification)
T169G (Tolerance Limits, Invoice Verification)
...etc.
Have a look at this fm.
If you do a "Where used" search of this fm you will see that is is called in:
Include LMRMPF1L
Subroutine SPERRGRUND_S
if you have a look at this subroutine you will see that there is an exit there:
CHECK PX_DRSEG-SPGRS NE SPACE.
SY-SUBRC = 0.
CALL CUSTOMER-FUNCTION '001'
       EXPORTING I_RBKPV = PI_RBKPV
                 I_YDRSEG = PX_DRSEG
       EXCEPTIONS CALL_FAILURE = 001.
CASE SY-SUBRC.
    WHEN 001.
      MESSAGE E271 RAISING PARAMETER_ERROR.
ENDCASE.
The exit is EXIT_SAPLMRMP_001.
then there is call to fm MRM_TOLERANCE_CHECK
within this fm there is an exit:
*------- Customer Exit ------------------------------------------------*
CLEAR: CHK002, SY-SUBRC.
CALL CUSTOMER-FUNCTION '001'
       EXPORTING I_BUKRS = I_BUKRS
                 I_TOLSL = I_TOLSL
       IMPORTING E_WERT1 = X169G-WERT1
                 E_XW1JA = X169G-XW1JA
                 E_WERT2 = X169G-WERT2
                 E_XW2JA = X169G-XW2JA
                 E_PROZ1 = X169G-PROZ1
                 E_XP1JA = X169G-XP1JA
                 E_PROZ2 = X169G-PROZ2
                 E_XP2JA = X169G-XP2JA
                 E_CHECK = CHK002
        EXCEPTIONS CALL_FAILURE = 001.
This exit is EXIT_SAPLMRMC_001
And within fm MRM_TOLERANCE_CHECK there is the possibiliy of an implicit enhancement.
question: why trying to flag field RSEG-SPGRS when you have tolerances available?
Best regards.

Blocking Reason for HU

Hello ,
We are using Blocking reason for HU. Means if you define blocking reason in packaging instruction you can see the same in HU03 ( Additional Data). Is anyone Knows where to put this Blocking reasons other that Packaging instruction?
Thanks,
Shailesh

HAve you searched OSS notes,
There are many if you search with MRBR as keyword.
I remember having seen one that fixed program errors where the blocking reason was not removed after a release

AP Invoice Blocking Reason

For Accounts Payable Invoices that have been blocked, i know that BSEG-ZLSPR is the Payment block key. For MM documents, where is the Blocking Reason stored ?

Hi,
The settings in MM area for Invoice Block reasons can be found in OMR9 and tolerance limits in OMR6.
Regards,
Kiron Kumar T.

Difference between deleting invoice blocking reason and releasing blocked i

Hi - in mrbr we have two options - one is to delete a blocking reason and the other is to release the invoice.
It appears that it is possible to delete the blocking reason and this releases the invoice for payment.
It is also possibel to releease the invoice without deleting the blocking reason and this has the same effect.
Why do both things appear to do the same?

Hi,
The both cases differ in approach, we use delete blocking reason if there is any block existing for the Invoice and after that if the system finds no other block on Invoice header ten the Invoice is automatically released, however if we go for direct release then only those Invoices are released which had blocking reasons but some business transactions have nullified the block already.

Cannot retrieve blocking reasons from mir4

i am trying to retrieve the blocking reason fields (spgrm, spgrp, spgrt and spgrq)from mir4 but when i look at the technical settings the field is in structure drseg. since i cannot fetch data from structure, i used the where-used list to find out other tables which include those fields.
as of now, the report fetches the blocking reasons from table rseg and bseg. i have to modify it in order for it to get data from mir4. how can i do that if as i trace the structure, both the table bseg and rseg uses those same fields but their results are different from the expected results in mir4? please help.

This may be because of shared buffer raw message are not in temporary file or data pool.

How to set delivery block in va01 by not use delivery block reason.

Dear SAP Gurus.
I have one scenario. I need to do delivery block on sales order while i create sales order via VA01.
Normally, I use delivery block reason in header and set delivery block in schedule line.
In addtion, i dont want to use above method and not use complete delivery (Tick on it)
So, I would like to know it has other way to do delivery block.
The cause is my manager do not allow to use this field from company's policy.
Please help me to solve this problem.
Thank you in advance for your kindly help.
Best Regards,
Surakit

Surakit,
Well, do you want to say that user should not manually user delivery block at header or sch line to block the doc or any other method manually done before saving the sales order.
In that case, for making default delivery block at header, in Sales doc type (TCode VOV8) in Shipping section, maintain a delivery block as 22-Statutory Compliance(even any other option available) or for Item based block on Sch line cat (TCode VOV6) maintain default delv block there.
Or if I misunderstood your requirement then we can wait & see other solution coming for the same.
Thanks & Regards
JP

How can I open a vi and show the block diagram?

Hi,
I am opening an vi using "Open VI Reference" and "Invoke Methodpen FP", but I want to open the vi and show the block diagram, but I haven´t found any method (Invoke Method) to do that and any property.
Any idea?
Thanks!
Gracinda

OK, I can come up with a reason. I have written a program that will search the entire VI Hierarchy of a program and update all of the descriptions for all VIs with the top level program part #, the name of the top level program that the VI is used in, the company copyright info, the ITAR notice, company address, the name of the engineer performing the update, along with the date and time. This will also place as a background image on all the VIs, a watermark of the company name, legality stuff and the copyright. It works very slick in that if there are thousands of sub-vis, such as what I'm working on now, it goes through all of them, makes sure the data is there as per company policy without having to open every one of them look at them and update or not whichever the case may be. The one portion that is tough is that the program will detect if there is a description written about what funtion the VI performs and if there is not a description, then it pops up a dialog requesting the user to write a description. The problem is that without looking at the block diagram for the VI, it can be nearly impossible to write a description for the functionality of the VI. So is there a way to programmatically open a VI, show its block diagram (this would only be in the case of a missing description) and then upon completion of the updates, close the block diagram? (I already open and close the VI programmatically in order to read the VI DESC and update as needed, but that is in the background and of course you can't see the block diagram).
Thanks,
Dan

In which Table we will see the Blocked sales order stock

I tried in MARD Storage Location Data for Material here i can able to see the unrestriced stock but i am not able to see the
blocked sales order stock.
Field : SPEME Blocked here blocked stock is not updating though we can see in MMBE
Can any one help me to find out the sales order stock
Note: sales order stock is different this i am getting in MSKA: Sales order stock
Edited by: balashowry raju on Sep 3, 2010 10:12 AM

Hi,
Are you talking about qty reserved by system for sales order wich are blocked for some reason like credit check? In this case, system does not block any qty for blocked order.
If you are looking for confirmed qty for sales order then you can see in CO09 transaction, confirmed qty against sales order.
Regards,
Mukul

Payment block reasons

Hi,
what are the settings i need to do for payment block reasons, i am working in quality management, when i don't approve the quality check, it is allowing for outgoing payment, and it should work like this once i approve the invoice and it should not ask for payment is blocked. Please provide complete config for payment block

Hi Sai
Payment block reason is assigned to differentiate among the reasons why invoices are not paid. You can define as many reasons as your business requires. However block is applicable for all Co Codes defined.
In payment block reason, you have 3 options:
Changes in payment proposals- If you select this, you can edit or delete the block at the time of Payment proposal
Manual payment block- This is to restrict the clearing even if the incoming or outgoing payment is made via manual entry
Not changeable- This cannot be cancelled or editable by the user.
Hope this clarifies your question.

Payment Block Reason Overview Screen

What does "Not Changeable" Indicator Does in Payment Block Reasons Screen
What happens if we check that
A detail answer is well appreciated.
Harsh
Moderator: Please, avoid asking basic questions

Dear:
I think you are talking about the settings in Tcode OB27. If the checkbox for 'Not Changeable' is activated you cannot change the Payment block directly and vice versa . Manual payment like in F-53 does not consider payment block unless you do not configure it in OB27. You can latter release this invoice only using MRBR. This is for your information.
Regards

Payment block reason

Hi Gurus,
can anyone explain where payment block reasons are used?
pls help
Regards
ravi

HI,
Manual payment block
If you manually select a payment block from the list field to block an invoice for payment, the payment block field in the header of the invoice document is marked with the appropriate indicator.
Blocked due to differences
If invoices are to be blocked automatically due to differences in the invoice items, the system enters the payment block R in the vendor line of the Accounting document. The field in the header of the invoice document remains empty.
Random payment block
Invoices that do not show any other blocking reason, can be blocked in accordance with the random principle. In Customizing for the Logistics invoice verification, you can set the probability for the block. The indicator for the logistical payment block is entered in the header of the invoice document.
Thanks and points
Vasu.

Unchange the Block Reason in FB02/FB09

Similar Messages

Maybe you are looking for