Reason code entry in BAPI_GOODSMVT_CANCEL

Hi Experts,
I am need of canceling GR for a material document. When I accomplish this using BAPI_GOODSMVT_CANCEL, it is asking for reason code entry. But there is no provision in this BAPI for reason code entry. Please advise to proceed further.
Thanks in advance,
Viven

Use this FM
MB_CANCEL_GOODS_MOVEMENT
GIve the reason in ET_MSEG table...
The BAPI also internally uses the same FM
Reward if helpful...

Similar Messages

Reason Code automatically defaulted in dispute created from FBL5N

Hi Guys,
Your help would be greatly appreciated here.
We have a situation where ONLY for document type RV (Billing transfer), the reason code is defaulted to "AA" awaiting audit. This happens when I select a particular customer invoice from FBL5N and create a dispute from there. While creation of dispute, it does not ask me for any reason code entry and is not even there as an input field, but when I save this dispute and view it in the corresponding FI document, the reason code gets populated as AA in additional information tab of financial document.
We want to change this reason code from AA to DI but we dont seem to find where to change this.
I have revisited every possible configuration for dispute management and even checked "Define Default Values" in dispute management and we have not mentioned AA as default value anywhere. But we are not able to find it. Note: This is happening only for document type RV and for other doc types no reason code gets updated.
Is there any configuration which I might have missed?
Regards,
Sweta

Hi Mark,
I was hoping you would respond to this considering your experience in this. I have checked for substitutions already but there is no such substitution which exists. Our technical team is trying to find out if it is hardcoded but they have not had any clue so far. Some routine would hardly be a case because the accounting document is already existing and after this the dispute is being created. i.e. the dispute is not getting created on the SD side nor it is getting created at the time of transfer of docs from SD to FI. It is purely during FI-Dispute link up after SD part is over. However, I will still tell my technical team to look into it.
Regards,
Sweta

BAPI_GOODSMVT_CANCEL reason code

Hi,
Iam trying to use BAPI_GOODSMVT_CANCEL bapi to cancel GR for movement type 101. In my system Movement for reason code is mandatory , i should provide the reason code for cancel. But i dont have any import paramater in BAPI_GOODMVT_CANCEL bapi to pass the reason code.Based on my requirement i should use this BAPI only. What changes i should do in BAPI, pls suggest.
Regards,
Dhanunjaya Reddy

though i dont solved it, i dont want to continue.

Error: Reason codes with automatic charge-off are not permitted here(F-28)

Hi All
I creted a reason code in obxl t-code and assigned a gl code in OBXL transaction code, But when I am trying to clear a payment with reason code in F-28, System is throwing the following error..Can some one tell me why i am getting this error?
Reason codes with automatic charge-off are not permitted here
Message no. F5605
Diagnosis
The reason code entered is designed to ensure that the payment difference amount is posted to an account specially set up for this purpose. Postings of this nature usually require additional specifications (e.g. tax code, business area). If the difference stems from a single open item, the necessary specifications can be taken from that item. In the case that led to this error message, however, the difference does not stem soley from one item, which means that this method cannot be used.
System Response
The reason code entered is not accepted.
Procedure
You can either select a different reason code, which would create a new open item for the customer or vendor OR write off the difference using the function Charge off diff.. This function either takes you into a pre-configured account assignment model or into the document overview. From here you can enter the required difference postings.

Hi Venkata,
It seems while entering the payment (partial payment / residual items) ... you are clearing multiple items with differences. (e.g. if the difference amount is $30, then may the difference consists of two invoices underpaid by $15 each). In this scenario, F-28 doesn't know which additional account assignment fields should be picked up ... hence the error.
First of all, to validate that this indeed is the case, try clearing a payment with the same reason code where difference can be attributed to a single invoice. If you still get an error, then there is some other problem.
Then, to take care of a the business scenario where the difference can indeed be due to multiple documents, select "charge off difference" option and create an entry to post the difference as necessary.
HTH,
Manish Patel
Sr. SAP Solutions Consultant

Limiting or control for Residual payment with reason codes

Hi FI Gurus,
When we are received or making payment to customer or vendor, sometimes we need to clear the invoice by receiving or making payments with small differences through residual payment. Is there any control for limiting residual payment.
Lets have an example
invoice posted for 1000
customer dr 1000
sales       cr 1000
Partial payment recd 500
cash/bank dr 500
customer cr   500
final payment received 350 and balanace amount adjusted with residual payment by defining reason code like rounding off difference. So in this case accounting entry will be
customer cr 350
rounding off diff 150
cash/bank 500
being final payment agaisnt invoice
My question:   Is there any way to restrict the residual payment like 10% or 20% of total invoice i.e. 100 or 200 and not more than 20% ? other wise sometime user may adjust any amount may be 100000 through this way by putting the same reason code, which is not fair.
I checked SPRO setting but i did not get anyt setting relating to above case.
If any body know, please let me know? Thanks in advance
Regards,
Prakash

Hi Lawerance,
Thanks for reply.
But I am looking for amount adjusted through residual with reason code. I dont think there is any limitation or control in the SPRO standard setting. Tolerance is preventing user to post document for more than a specific amount. But my question is something different.
I want to control the user for adjusting amount from residual tab with selecting reason code. In other words user should not adjust more than some limit with residual payment by selecting reason codes. Thanks.
Regards,
Prakash

Payment Difference by reason code charge to separate GL Account

Dear All
We have set reason code for payment difference with indicator charge to separate account. Also we assign separate account for each reason code in OBXL. When we try to post incoming payment with difference and assign the reason code system ask to do the account determination for Transaction ZDI. We already have settings for ZDI with reason code. When we enter one more entry for transactions ZDI without reason code system charge it to the account but in this way we cannot achieve our objective to post the difference to different account according to reason code.
Please advise
Thanks and Best Regards

What do you mean by "hierarchy"? I'm not aware of any hierarchies within Transaction Management.
You need to set up an account assignment reference for the different portfolios (IMG activity "Define Account Assignment References").
Then you need to set up the determination logic for assigning the account assignment reference to the transactions based on portfolio (IMG activity "Define Account Assignment Reference Determination (OTC Transactions)" or "Define Account Asst Reference Determination (Securities/Listed Derivatives)", depending on product type.)
Finally, you need to set up the account determination to assign the GL accounts to the different account symbols for each account assignment reference (IMG activity "Define Account Determination").
Regards,
Shannon

Reversal Reason Code not displayed in document -FB08

Hello,
I have reversed the FI document using the transaction code FB08. While reversing I have given the SAP standard reversal reason code as 1. A new document was created on reversal of document.
But Reversal reason code '1' is not getting displayed in FB03 or GL line item report FAGLL03. I have checked the Field staus of the Posting key as well as of the GL accounts, at both the places "Reason code" is optional entry field.
Can you please suggest where/How to see the reversal reason in the document reversed through FB08.

Hi Prasanna,
First of all go to Table BKPF & check for the field STGRD value for the concerned document.If it has value then you will get the value for Reversal Reason in FB03.
I think you have mistook selecting the Reversal Reason in the layout because there are 2 different Reversal Reason fields with the same name. So select the correct field (BKPF-STGRD) from the layout.
Hope it solves.
Regards
Andrew

CAD UCCE Reason Codes Question

In UCCE CAD 7.5.4 and later Spanlink came out with a new feature where a agent can change thier "Not Ready" reason code without going "Ready"->"NotReady". I have a customer who is running 7.5.6 and does not like this feature and would like to turn it off. There is nothing in Cisco Administration Desktop application that controls this (i.e. enable / disable of this feature) Does any one know if there is a Registry or configuration file that can turn off this feature? - Thank for your help! - Jim

Not as far as I know. Haven't asked TAC or anything yet though. It's annoying because when going Not Ready > Not Ready it doesn't write an entry into the Agent_State_Trace table, only the Agent_Event_Detail which one of my clients needed to use for reporting..

Reason code for short payment received from Customers

Hello
We are on ECC 6.0 without application of any enhancement package.
Requirement is to capture reasons of short payment received from customer and generate a report based on such reason codes.
Reasons of short payment received could be - Adhoc payment; Excess billed; Tax deducted at source (TDS) on freight / service charges and Bank charges etc.
Let me know relevant configuration required.
Would reason codes be captured during incoming payment entry or customer account clearing?
Thanks.
Vimal, India

Hi Vimal
Following is the configuration for Reason code for customer payments. It can be short payment, over payment or discount not allowed.
First step is to define reason code. You do this in Financial Accounting (New >Accounts Receivable and Accounts Payable>Incoming Payments>Incoming Payments Global Settings>Overpayment/Underpayment>Define Reason Codes
Define reason code , short text, long text and assign it to correspondence type. (please note correspondence type settings needs to be done first). There is a column c which is Indicator: Charge off difference via separate account set this if you want to post the difference to seperate account during clearing customer open item.
The second step is to define accounts for payment difference.
Financial Accounting (New >Accounts Receivable and Accounts Payable>Incoming Payments>Incoming Payments Global Settings>Overpayment/Underpayment>Define Accounts for Payment Differences
Assign G/L accounts against reason codes.
The third step is Define Reason Code Conversion Version
Financial Accounting (New >Accounts Receivable and Accounts Payable>Incoming Payments>Incoming Payments Global Settings>Overpayment/Underpayment>Define Reason Code Conversion Version
In this step, you make the default settings you need for the manual incoming payment processing via payment advice notes. If differences between the payment advice item and the total of the allocated open items occur after selecting the open items, you can enter a reason code in the payment advice item. This represents the reason for the reduction of the payment amount specified by the paying person.
Create version 001 and name for it.
For correspondence type create or assign relevant form and print program in global settings> correspondence
Once you have these settings you can insert appropriate reason code while clearing customer open item .
You can print correspondence via T-ode F.62 on a monthly basis or wekly basis.
Hope this helps.
Thanks
Sanjeev

Payment Advice EDI - Reason Codes

HI All,
At the time of configure the Payment Advise through EDI, Is it Reason Codes configuration is Mandatory.
Ex :
Case 1 :
SAP - Customer Invoice : @ 1000
Customer Account Dr - 1000
To Sales Revenue       - 1000
Incoming Payment Received file from EDI Transfer : @ 1000
Bank Main Account Dr - 1000
Customer Account or   - 1000
Case 2
SAP - Customer Invoice : @ 1000
Customer Account Dr - 1000
To Sales Revenue       - 1000
Incoming Payment Received file from EDI Transfer : @ 900
Will it accounting entry generate or will it stop due to the Partial Incoming Amount.
In this case Reason Codes will work. So Where can we insert the reason codes to capture the differential amount between the Invoice & EDI Incoming receipt
Regards
Raj

Hi Satya
I think you are expecting payment advice to your company from bank.
For this you need create partner profile as BANK TYPE .
ANSI X12 txn is 820 - Payment Order/Remittance Advice
Please tell me is it ALE or EDI ?.
If it is EDI we are reciving the file from EDI Subsystem
It it is ALE means we are reciving the file from SAP R/3 only(genral practice).we can use ALE communication between SAP to NON-SAP systems also but when we are connecting to other company people will prefer EDI.
thanks

Reason Code for Reversal

Dear Experts,
When I am doing reversal of any document using FB08, I am giving reason code as Cheque Bounce or some other reason code. But when I am viewing the same document, the reason code is not available.
I have checked the same in BKPF but the same is not available there also. Please advise why the reason code is not posted in table.
Thanks,
Deb

I have tried with all fields you have mentioned, but unable to find the entry for the reason. I think there could be some problem in "Reasons for Reversal" settings in SPRO. There have 2 combination of selections, 1 for negative entries and another is for Alternative Posting dates. I have also tried with all the combinations, but still it is not working. Please advise if there is some other combination or assignments for these codes to somewhere to get the desired results.
Thanks,
Deb

Extending resource status and reason code category

Hi Experts,
I have a couple of questions regarding the extensibility of status and reason codes in ME15.0 in the context of machine integration:
1. Is it save to add new status fields (records) in WIP.STATUS for STATUS_GROUP="RESOURCE"? Is there any impact, if a resource doesn't match one of the predefined status values?
2. The "logResourceStatusChanged" service creates entries in WIP.RESOURCE_TIME_LOG but not in WIP.RESRCE. That way, it is possible to get different status values in both tables at a given time. Do you see any negative impact resulting from this data inconsistency?
The service "ChangeResourceStatusRequest" is not suitable in our case, since it doesn't provide a timestamp as input parameter for the status change. And even if it would, the prevention of a "sfc complete" when the status is "unscheduled down" is inconvenient for our customer. The scenario is, that the customer wants to complete the quantity produced until the machine broke down (assume lot production).
3. Is it possible to add new "categories" in addition to the predefined values in WIP.REASON _CODE? What is the impact?
regards,
Georg

Hi Georg,
I cannot give you a precise yes/no answer - so this is just to share some info.
- I've heard about some customer who implemented custom statuses. When a new status simply was added in the database, it did not affect a core functionality. But I do not know what happens if this status is assigned to a resource and then a core fucntionality is triggered. There might be some validation which could fail. But it is easier to test specific cases as how you are going to use SAP ME, and I doubt any developer will be happy to run a full analysis of code to answer your question.
- The new statuses need to be considered for loading via IDAT and adding into LocaleSpecificText properties file.
- As to custom categories of reason codes, I guess there are only few places where system behavior is tightly connected to specific predefined reason codes. So, I'm inclined to believe that adding reason codes and categories will not harm.
Regards,
Sergiy

URGENT: Reason code in Material document

Dear all,
We processed a thousand 551 movements without reason code.
The user strongly NEEDs that field populated.
I tried to modified the document with MB02 but, the field 'reason code' does not appear.
I looked in configuration trying to find a way to open it for input when process with MB02 and I did not find it.
This has BIG implications in our company and the user is thinking in updating directly MSEG with the reason code.
Does any body know how to open the field in MB02 OR if there is any implication in updating field Reason code (MSEG-GRUND) directly in the database?
Thank you.
Monica.

Monica,
I don't think it's possible via MB02. In general, changes to a material document are very limited (except a few text fields). I would suggest to cancel the movements and redo them correctly instead of doing a direct table update.
If the volume is high, you should try to use LSMW or similar methods. Have a look into BAPI_GOODSMVT_CANCEL and BAPI_GOODSMVT_CREATE.
Hope this helps.
H Narayan

Reason Code Functionality

Dear All,
Experts.
I want to know about Reason Code. What is practical functionality of reason code ?
Here is my understanding as follows :-
Suppose I am posting one bill of Rs. 12,000/- against that I am receiving Rs. 14,000/-.
So if I use reason code, will my entry & effect like this ?
Bank A/c Dr 14,000
customer A/c Cr 12,000
Exchange Gain A/c Cr 2,000
( Being exchange gain of Rs 2,000/- )
For this functionality Reason code is used ?
1 ) In addition to this will Rs 2,000 generate one more residual line item in customer account ? 2 ) or account will be clear?
3 ) Where I can link the reason codes ? 4 ) It is at customer master level or document level 5 ) Reason code is Manual assignment or Automatic assignment ?
Experts your help on this will be great.
Regards,
Sharvari Joshi.

Dear,
Chintan.
Thank you again for focusing on my questions. Can I link the reason code to customer while taking the payment from F-28 ?
Or at any other T.code I need to use for using Reason Code ?
1) Define reasons Codes
2) Define accounts for payment differences
3) Define std reason code for clearing w/payment advice notes.
4) Define Reason code for conversion version
5) Define conversion of payment differences reason code.
are the only steps to configure reason codes ?
Your help on this will be great.
Regards,
Sharvari Joshi.

Reason Code in FBL3N

HI,
I have done a posting through F-02 and mentioned Reason Code at the time of entry.
When I check FBL3N, Reason code is not getting populated, what could be reason?
Regards,
Meenakshi

Hi,
In FBL3N, go to change lay out (Ctrl + F8), from the "Hidden Fields" section select "Reason Code" and move to left hand side > Click on Copy button. You will see Reason Code appearing in the screen.
Regards,
Ravi Kumar
Edited by: Ravi Kumar on Nov 7, 2008 1:28 PM

Reason code entry in BAPI_GOODSMVT_CANCEL

Similar Messages

Maybe you are looking for