We are facing an error on the screen in the compensation manager responsibilty in Manage Transacations --> Create
When we try to create a new transaction, we get the error "Processed date must be within open periods."
Though we have setup the primary ledger the accounting calculator as well as the open periods and the date being selected in the Processed Date is within the open period specified but still we are facing this error
Also, how will be know that our Operating Unit is attached to that particular ledger.
If we can confirm that the OU selected is associated to the ledger for which we have defined the open period. Can this be the reason or there is some other reason. Kindly help.
Please check to see if compensation periods are open in OIC.
navigation:
Compensation Manager> Setup>Maintain Compensation Periods.
Thank you everyone. I was missing the general parameter setup.
Incentive Compensation Administrator
Configuration Workbench > Application Parameters > Go To Task > Setup General Parameters
And Yes after that I have to open the compensation periods as mentioned by vijay bhamidipati
Related
I am using classic asp for a web application. I am running the web application on internet explorer.
I had developed few reports related to sales data. All the sales report are linked to Sales Dashboard. Every report has some selection criteria like customer selection date period selection product group selection and other few.
Now the problem which I am facing.
I open a total sales report for the entire year which takes almost 15 minutes to load on screen. while the report is executing if I try to open any other from the sales dashboard the page with selection criteria will appear after the first report is completely executed. If I copy the link location for the second report and open it in new window of internet explorer it will open normally.
I am not able to trace the problem did anyone had face the same problem.
First, I agree with this comment posted under the question:
IIS/ASP only allows one concurrent request per session. This is why the second request does not happen until after the first one completes. If you open a new browser instance or a different browser then this is treated as a different session.
Second, if all that is being asked here is whether other people have similar issues or not, then the answer is yes, due to what johna said in the comment.
If you're looking for a way to get around that for yourself, the way described in the comment (open a new browser instance or a different browser) will work.
However, if you're after a way to bypass the 15 minute wait time entirely, give some though to preparing the data before the report is called. What I mean by that is either schedule the report to run after close of business each day and store the relevant HTML or data separately, and/or provide a button to prepare the report based on current data which can be run whenever the user wants.
I have been trying to import customer master through data management tool in AX7 using "Customers" standard data entity, I have marked "Auto-Generate" for customer account field. And I am facing a number sequence error while the data gets inserted into staging. When I check the execution log I see the below error.
"Issue exists in auto generation of number sequence
Issue exist in generate staging data
'4' 'Customers' record(s) inserted in staging"
I checked number sequence setup for Customer account and it is proper it is as below:
Note:
Gives the same error irrespective of Continuous is marked or not for the number sequence code.
Any quick inputs would be appreciated!
Thanks Fh-Inway!
I have figured out the issue, and it's an issue with standard AX. An application hot fix (Metadata) is available for this which can be found in the LCS as a part of AX update2. I have installed it, tested it to be working fine.
Not sure whether I can share the Hotfix KB Article number here for the same.
Note: That hotfix has a common fix that addresses auto-generation of number sequences across all the data entities.
When trying to submit a Transaction for a Partial Settlement, I'm getting the following exception + message:
Exception of type 'Braintree.Exceptions.AuthorizationException' was thrown.
There is nothing else to explain where I've gone wrong.
This is how I'm making the API call:
BraintreeHandler.Gateway.Transaction.SubmitForPartialSettlement(“transaction_id”, amount);
I know the Transaction Id is correct, because I'm loading the Transaction information beforehand. I'm also always using an amount less than the transaction total.
BraintreeHandler.Gateway.Transaction.SubmitForSettlement(“transaction_id”, amount);
The above works fine with an amount, but I don't want to submit the Transaction for settlement as I'd like to retain the ability to partially settle.
For example: If I have a Transaction Amount of £50 with a status of "Authorized", I'd like to be able to settle for £20, £20 and £10 on three separate occasions. With the SubmitForSettlement() method I can only settle for the initial £20 before the status is updated to "Submitted for Settlement". After this I can't perform any more partial settlements.
Information pertaining to the SubmitForPartialSettlement() method is conspicuously missing from the Transaction docs on the Braintree developer site. Has the method been deprecated? If not, how can I make use of it?
Full disclosure: I work at Braintree. If you have any further questions, feel free to contact support.
SubmitForPartialSettlement is a feature currently being tested and is not available to all merchants at this time. If you would like to request multiple partial settlements to be enabled for your account, please reach out to Braintree support or your account manager.
For the time being, you have the correct solution in SubmitForSettlement, passing in an amount less than or equal to the transaction amount. You will only be able to settle once.
I need to understand the accounting entries that are created in Oracle ebs. For example, when we talk about a standard P2P cycle, there are certain accounting entries created right from the moment a purchase order is created, approved and received.
I have basic knowledge of debit and credit entries. But when it comes to making debit and credit entries in Oracle apps, when I look at the accounts being used, I can not apply the basic dr cr entry rules to the accounts.
Please advise on this. Kindly also suggest some resources from where I can obtain this information.
This isn't a simple answer as the DR and CR entries are all driven by the accounting setup. To use your example, when a PO is created, very little accounting is done. It isn't until the line is received and Create Accounting is run that debits and credits are really applied based on how the accounting rules are set. If you were to open a PO, click "All Distributions", select a line and then click Tools > View Accounting Events, you'll see the detailed debits and credits that the accounting setup has created.
I'm not sure what your role is (developer, analyst, accountant etc.) or your experience level, but I would suggest you familiarize yourself with the accounting setup of your organization to be able to truly understand it. My suggestion is to get a Financial Super User responsibility in your development environment and ask one of your Financial Analysts to show you the basics of your account setup.
If you really want a deep dive, login to your My Oracle Support account and start looking at the documentation (Doc 1597048.1). The user guides are exhaustive but very helpful when you get the right one.
The debit and credit depends on the accounting rule setup.
In simple terms:
Inv Validated:___Dr-------Cr
Inv Exp...............100
Liability...........................100
Inv Paid:________Dr-------Cr
Liability........100
Cash................................100
There can be several steps in between depending on the Accounting rules, like Encumbrance accounting.
I have a charge code called FREIGHT set up with the following configurations. Under Credit, I've specified a ledger account of 4800.
I now create a Purchase Order, confirm and go through the whole process, and then try to invoice / post it.
I'm presented the following error:
"The combination 4800- is not valid for the account structure MYACCOUNTSTRUCTURE"
So it's been identified that AX is attempting to use 4800 from the aforementioned charges code field MarkupTable.VendorLedgerDimension.
In the code, it crashes in the PurchFormLetter.run() method, and if I did further it goes into the SysOperationController\pack super(); class before it crashes.
Now, if I were to change my account from 4800 to for example 2100, then the invoice goes through fine, which is good.
My question, and what I need is to find out what class / where in the code is this happening during the invoice post process that AX is trying to use this MarkupTable.VendorLedgerDimension field. I need to access that part of the process and modify that value (obviously 4800 is just the display value) to be something else.
If anyone needs more information for background, I need to keep the account for FREIGHT at 4800, while setting the actual financial dimension to the financial dimension on the line item. I've been debugging and looking all over the place for where this process occurs, but have had no luck so far.
If anyone can point me in the right direction, it would be very greatly appreciated.
Thank you.
Check what dimensions are mandatory on this account. Then set financial dimension on invoce lines.