Reason Code for MI07

Hi MM Guru,
I have created a inventory count document no: 100025069, When i try to post the difference in MI07 i need to have a reason code for the transaction. This is scrapping and movement type is 702. When i search for the code it does not apear any 702 codes i can use. Please have a look what can be done.
Thanks in advance,
Iram

Hi,
Go to OLMB and here crete the general reason code for material sdjustments , means the Poor quality , Breakabel or some other reasaons.
If u donts want that fiels as mandatory , make that one as optional field in screen layout og MIGO.
Regards,
Andra

Similar Messages

User exit to default reason code on MI07

Hi MM Experts,
Am an ABAPer and need your expert advice on this. For some reason I have been asked to default the reason code on MI07 screen with a certain value as soon as the user gets on the screen. I have not been able to find a user exit where I can default the value on MI07 for reason code.
All MM experts can you please suggest a user exit where we can do this.
Regards,
Saket.

Dear Saket Tiwari & Dëv Päträ
I think I've given you the not clearing impression. i mean that T-Code OLMB is for "Inventory Management and Physical Inventory" configuration. (I think that you already know about it)
1) Go to T-Code >> OLMB > Physical Inventory > Default Values for Physical Inventory &
                             OLMB > Physical Inventory > Field Selection for Physical Inventory
    Pre-settings for entering physical inventory documents
Reason for inventory difference
     The default value you specify here is only displayed when you enter an inventory difference
     without reference to the corresponding document. But you can also change the default value.
2) and You can control "Filed selection for Physical Inventory" such as MIGO filed selection.
I think that before finding Technical Enhancement Spot, You can consider Configuration Control for your process.
I hope that my options will be helpful for your project.
Regards,
Jeong, Yeong-Chul

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

Where to configure the reason code for payment differene

Dear Experts,
I did the settings in obxl with reason code option and changed the screen layout for the postings keys for payment difference as mandatory. while doing the account assignment in obxl system asking the reason code for payment difference. Where to configure the reason code any t.code is there, please guide me.
J.francis

Just Go SPRO>IMG>Financial Accounting (New) >Accounts Receivable and Accounts Payable > Business Transactions > Outgoing Payments > Manual Outgoing Payments > Overpayment/Underpayment > Define Reason Codes (Manual Outgoing Payments)
There you have to create Reason Code
Now go SPRO>IMG>Financial Accounting (New) >Accounts Receivable and Accounts Payable > Business Transactions > Outgoing Payments > Manual Outgoing Payments > Overpayment/Underpayment >Define Accounts for Payment Differences (Manual Outgoing Payment)
Here assign GL
Best Of Luck
Tanmoy

OTL: Timecard Audit Template require reason code for all transaction.

We are currently using OTL with CLA template with interface time entry from external system.
When monthly time entry interfaced into OTL each employee have to review and update their time and submit to manager, but when process to audit template they has been forced to update reason code for all transactions.
We suppose to update the reason code only for the modified transactions. Please help me.
Nonny.

nondhasid,
If you are not modifying those records which are asking for a reason field to be filled, then it should be coming from the Late setup. Check the CLA setup.
--Shiv

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

Void Reason Codes for Pre Numbered Forums

hi
in IMG we have the void reason codes. I did maintain them.
But when I ran the IDCP to remuber the form, there is no where it asks me for void code for the existing one?
is there a different tcode to handle this process of voiding the invoice so that we can track it in sales ledger
thanks
SAP245

Hi Ms. Monica
I am having the same problem....can you please let me know how you solved this issue?
My email is [email protected]
Please help me...
Thanks

Reason code for Firefighter

Hi Guys
Can you help me with some examples of reason codes that i can configure in Firefighter
Parveen

Hi Parveen,
The reason code is depends on your requirement like why the fire fighter will do the fire fighting.
And the example you asked will be like
Reason Code.................Reason Code Description
MM_FIREFIGHING .........MM MODULE RELATED FIRE FIGHTING
SD_FIREFIGHTING .........SD MODULE RELATED FIRE FIGHTING
You can give anything of your choice
Regards,
Sudip...

Function module to change the reason code for status in a Opportunuity/lead

Hi,
What is the function module to change the opportunity reason. I was able to change the status using the crm_order_maintain but How can I change the reason for that opportunity.
Thanks
naveen

You can use CRM_ORDER_MAINTAIN and populate the parameter IT_SERVICE_OS
or use BAPI_OPPORTUNITY_CHANGEMULTI and populate the parameter SERVICE_OS.
BR,
Florin

SQL to retrieve faulted instances and fault reason code for SOA composites

Hi,
Could you please provide me some SQL which will retrieve composite faults with details on a particular period?
Thanks in advance.

SELECT ID, COMPOSITE_DN, STATE, CREATED_TIME FROM COMPOSITE_INSTANCE. You can add filters for created_time and state. Refer to this link for a list of composite states. https://blogs.oracle.com/dasoa/entry/list_of_all_states_from

Two deductions for invoice with same reason code posted as one line item

Hi
We have a scenario wherein we are taking two or more deductions on the same invoice and are using the same reason code which have a setting of charge off.
SAP system displays the FI posting with same reason codes with charge off setting as one line item.
However we want the FI Posting to display separate line items per deduction and not combine amounts of deductions based on same reason code with charge off setting.
Any comments are appreciated.
Edited by: Kirti Bhardwaj on Jul 24, 2011 9:46 AM

Hi,
you can use different reason codes in distribute differences screen once you have fist selected one reason code for one invoice.

Documents not coming in the report taken for reversal reason code

Hi,
We have defined the various reason codes for document reversal.
When we try to take the report based on the reason code in FB03 or FAGLL03, the reversal doucment is not coming up.
Is there any setting for it? or how to get that report? We need that report to authorize the reversals.
Thanks,
Pratap

Hi,
Please note that In standard SAP, the reversal reason code gets stored in the original document which is reversed. It does not get stored in the reversal document.
You can get the report based on the field STBLG (Reverse Document Number) and STJAH (Reverse document fiscal year).
This will be filled up for both original document and reversal document. And the clearing document number will be same for both the documents, so you can easily link the two documents in FAGLL03 output layout using sorting based on clearing document and filtering based on the two fields given.
Regards,
Gaurav

Capturing change code/Reason code in CAT2 transaction for time change

Experts,
Wanted your suggestion and expertise in a solution where in CAT2 if a user changes the time/wbs element/tax area/work type he should be forced to put the reason code for change. The change event would populate/capture the change code, reason for change at cell level in CAT2
Your pointers would be of great help

The following enhancements are required to achieve the new pop up window functionality:
1.     A new customer field should be added to the CATS time entry screen in the CATSDB.
2.     A new check table should be created in CATSDB containing the allowable drop down entries for the new field.
Customer fields are inserted into the CI_CATSDB structure. This structure is contained in the database table for the Time Sheet (CATSDB).
Steps:
1. Create a customer project using the SAP enhancement CATS0005.
2. On the initial project administration screen, select the Enhancement components field and choose Change.
3. Select the entry CI_CATSDB and choose Edit -> Components.
4. Create the structure CI_CATSDB.
5. Insert the new field to the Time Sheet database table into the structure.
    Select the data dictionary type CHAR
6. Check and save the structure.
7. Activate the structure.
8. In the Cross Application > Time sheet section of the IMG Choose Make field assignment.
9. Assign the new field to the view.
10. Assign a number from 1 - 10 specify the name of the field, u201CChange Reasonu201D.
Then Conditions Check for New Field:According to requirement

Reason code SE is not defined

I have created credit memo request in VA01.
i have generate biling documnet (credit memo) VF01 but accounting document not generate.
it is giving error message when i am trying to release manuvally.
"Reason code SE is not defined"
Message no. F5596.
please help what can i do for posting accounting document.
Thx
k.Satish

HI,
In credit memo request VA02 mode please enter reason code for that document and then try to recreate credit memo..
Because in your case reason code is mandatory and it is not maintained in credit memo request thats why it is not copied into creidt memo. So please maintain that and then check once agian...
Regards
sankar

Siebel CRM Reason Code Commands

We are needing to enable some commands on the Cisco CTIOS Siebel connector and just not sure where they are enabled or edited at.
We are using connecter provided by CISCO for CTI between Siebel and CISCO. Connector provides the enabled command to Siebel that siebel can send as device command like "DeviceCommand = "ChangeNotReadyState"" using communication configuration DEF file.
Currently we have business requirement:
CTI agents can set their state to NOT READY on a click of button with reason code selected by the agents irrespective of there current state.
We configured the button, but the button is enabled only when the device command "ChangeNotReadyState" is enabled. Can it be possible to enable this button always and we can are able to change agents state at CTIOS level(CISCO)? Can we send "ChangeNotReadyState" command to CISCO irrespective of agents current state
Here is what we have done so far:
We configured DEF according to ORACLE support recommendation (ID 543337.1 listed below in this mail)
RELEVANT PARTIAL DEF FILE:
[Command:DSC_NOTREADY_POP_EXE]
   SubCommand_1 = "DSC_NOTREADY_NOPOPUP"
   SubCommand_2 = "DSC_NOTREADY_POPUP"
   SubCommand_3 = "CleanDashBoard"
   Comment      = "YQ8279: Add for Direct not ready Button Aug2012"
   Description = "Not Ready"
   ExecuteAll   = "TRUE"
   Hidden       = "TRUE"
[Command:DSC_NOTREADY_NOPOPUP]
   Comment       = "YQ8279: Add for Direct not ready Button Aug2012"
   Description   = "Not Ready"
   DeviceCommand = "ChangeNotReadyState"
   FilterSpec    = "[$GetCommandStatus(ChangeNotReadyState)]= 'Enabled'"
   Hidden        = "TRUE"
[Command:DSC_NOTREADY_POPUP]
   Comment       = "YQ8279: Add for Direct not ready Button Aug2012"
   Description   = "Not Ready"
   DeviceCommand = "ChangeNotReadyState"
   FilterSpec    = "[$GetCommandStatus(ChangeNotReadyState)]= 'Enabled'"
   Hidden        = "TRUE"
   CmdData       = "PopupforReason"
   [CmdData:PopupforReason]
      Comment          = "YQ8279: Add for Direct not ready Button Aug2012"
      Param.ReasonCode = "[Name]"
      SelectApplet     = "Transfer Multiple LOV Popup Applet"
      SelectBusComp    = "List Of Values"
      SelectBusObj     = "List Of Values"
      SelectParam      = "TRUE"
      SelectQuerySpec = "[Type] = 'REASON_CODE' AND [Active] = 'Y'"
      SelectTitle      = "Please select the reason for changing status to Not-Ready"
So with above configuration suggested by oracle support we are sending "ChangeNotReadyState" device command twice in a manner so that it will be processed one after the other. But it is not happing, second command is not going through as its not enabled after Siebel issued it once. Please see below logs and highlights.
SCOMM LOG: <In Time Context >
ChangeNotReadyState Command is enabled (status = 16)
see image 1 on attached doc
Now user applied the command once :
See Image 2 on attached doc
Now "ChangeNotReadyState" device command is disabled .
Can we make it "ChangeNotReadyState" enabled via connecter always by making some registry setting or some setup.
See image 3 on attached doc
Oracle Support Suggestion:
Not able to select Not Ready Reason Code [ID 543337.1]
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_afrLoop=485718774714219&type=DOCUMENT&id=881215.1&displayIndex=4&_afrWindowMode=0&_adf.ctrl-state=dhq5nrae7_147
Symptoms
In the current production we are having some CTI agents facing problem with picking the AUX Codes (Reason Codes) when trying to change status for Not Ready.
Some of the agents reported that they can NOT pick the reason codes ( probably the icon is disabled for some reason at some point of time). I tried to reproduce the problem, but not happened.
Our objective is to not receive the call and make the agent click the AUX Code (Not Ready Reason Code).
Cause
Users were not able to pick the auxiliary code (reason code) at Siebel web client under using Genesys Gplus 7.0.000.1. Agent objective was to not receive the call and be able to click the AUX Code.
During the operation of selecting an auxiliary code (aux code dialog open or not ready reason code applet) an incoming call reaches the agent before he decide which aux code to user not allowing selecting the reason code.
The GPlus driver at this point did not receive the not ready command and is in ready state for this agent allowing new calls.
Solution
Suggestion was to define first the not ready state for the GPlus with the default reason code = -1. Now agent is on a not ready state allowing enough time for agent to perform the selection.
Then we can call another communications command that starts the popup for the LOV of aux codes.
Here the agent will have enough time to pick the code with no more inbound calls.
The device commands for the command group are as follow:
[Command:NotReadyForGVoiceGroup]
   SubCommand_1 = "NotReadyForGVoiceStd"
   SubCommand_2 = "NotReadyForGVoiceAuxCode"
   SubCommand_99 = "NotReadyForGVoiceEnabler"
   Description   = "Set not redy for voice"
   Hidden        = "TRUE"
   ExecuteAll = "TRUE"
[Command:NotReadyForGVoiceStd]
   Description   = "Set not ready for voice"
   DeviceCommand = "NotReady"
   Hidden        = "True"
   Title        = "Voice not Ready"
   CmdData       = "NotReadyAuxCode"
[CmdData:NotReadyAuxCode]
   Param.ReasonCode               = "-1"   ; Check manual Gplus Adapter for Siebel 7—Deployment Guide page 241 for the value.
[Command:NotReadyForGVoiceAuxCode]
   Description   = "Seçect Reason Code for Voice"
   DeviceCommand = "NotReady"
FilterSpec    = "[$GetCommandStatus(NotReady)] = 'Enabled'"
   Hidden        = "True"
   HotKey        = "Alt+A"
   Title        = "Aux Mode"
   Profile       = "Gplus Voice1"
   CmdData       = "ReasonCodePopup"
   [CmdData:ReasonCodePopup]
      Param.ReasonCode               = "[Name]"
      Param.ReasonValue               = "[Value]"
      Param.StringAttributeExtensions = "ReasonCode,ReasonValue"
      SelectApplet                    = "Value Type Pick Applet"
      SelectBusComp                   = "List Of Values"
      SelectBusObj                    = "List Of Values"
      SelectParam                     = "TRUE"
      SelectQuerySpec                 = "[Type] = 'REASON_CODE' AND [Active] = 'Y'"
      SelectTitle                     = "Please select the reason for changing status to Not-Ready"

Thanks for your response Cherilynn,
You are correct for a vanilla agetn desktop. However, if the agent has to become available to move from one aux reason to another, the agent may get a call in that process. With customiization, we can allow changing from one aux code to another without having to make the agent ready. Oracle suggested a solution but to do this, we need to enable and modify certain parameters within Cisco. What we are trying to find out is where are these parameters set, ex: AgentWorkMode and AgentWorkMode2, ChangeNotReadyState...
ORACLE SUPPORT SR
Not able to select Not Ready Reason Code [ID 543337.1]
SymptomsIn the current production we are having some CTI agents facing problem with picking the AUX Codes (Reason Codes) when trying to change status for Not Ready.
Some of the agents reported that they can NOT pick the reason codes ( probably the icon is disabled for some reason at some point of time). I tried to reproduce the problem, but not happened.
Our objective is to not receive the call and make the agent click the AUX Code (Not Ready Reason Code).
CauseUsers were not able to pick the auxiliary code (reason code) at Siebel web client under using Genesys Gplus 7.0.000.1. Agent objective was to not receive the call and be able to click the AUX Code.
During the operation of selecting an auxiliary code (aux code dialog open or not ready reason code applet) an incoming call reaches the agent before he decide which aux code to user not allowing selecting the reason code.
The GPlus driver at this point did not receive the not ready command and is in ready state for this agent allowing new calls.
SolutionSuggestion was to define first the not ready state for the GPlus with the default reason code = -1. Now agent is on a not ready state allowing enough time for agent to perform the selection.
Then we can call another communications command that starts the popup for the LOV of aux codes.
Here the agent will have enough time to pick the code with no more inbound calls.
The device commands for the command group are as follow:
[Command:NotReadyForGVoiceGroup]
   SubCommand_1 = "NotReadyForGVoiceStd"
   SubCommand_2 = "NotReadyForGVoiceAuxCode"
   SubCommand_99 = "NotReadyForGVoiceEnabler"
   Description   = "Set not redy for voice"
   Hidden        = "TRUE"
   ExecuteAll = "TRUE"
[Command:NotReadyForGVoiceStd]
   Description   = "Set not ready for voice"
   DeviceCommand = "NotReady"
   Hidden        = "True"
   Title        = "Voice not Ready"
   CmdData       = "NotReadyAuxCode"
[CmdData:NotReadyAuxCode]
   Param.ReasonCode               = "-1"   ; Check manual Gplus Adapter for Siebel 7—Deployment Guide page 241 for the value.
[Command:NotReadyForGVoiceAuxCode]
   Description   = "Seçect Reason Code for Voice"
   DeviceCommand = "NotReady"
FilterSpec    = "[$GetCommandStatus(NotReady)] = 'Enabled'"
   Hidden        = "True"
   HotKey        = "Alt+A"
   Title        = "Aux Mode"
   Profile       = "Gplus Voice1"
   CmdData       = "ReasonCodePopup"
   [CmdData:ReasonCodePopup]
      Param.ReasonCode               = "[Name]"
      Param.ReasonValue               = "[Value]"
      Param.StringAttributeExtensions = "ReasonCode,ReasonValue"
      SelectApplet                    = "Value Type Pick Applet"
      SelectBusComp                   = "List Of Values"
      SelectBusObj                    = "List Of Values"
      SelectParam                     = "TRUE"
      SelectQuerySpec                 = "[Type] = 'REASON_CODE' AND [Active] = 'Y'"
      SelectTitle                     = "Please select the reason for changing status to Not-Ready"
Regards,
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_afrLoop=485718774714219&type=DOCUMENT&id=881215.1&displayIndex=4&_afrWindowMode=0&_adf.ctrl-state=dhq5nrae7_147

Reason Code for MI07

Similar Messages

Maybe you are looking for