Auto create account

Hi everyone,
I have been trying to create a URL to autocreate an account.
https://secure-ausomxXXX.crmondemand.com/OnDemand/user/DefAccountInsert?OMTGT=AccountEditForm&OMTHD=AccountNewNav&OMRET0=AccountHomePage&AccountEditForm.ZPick_1=%%%plCustomer_Rating%%%&AccountEditForm.ZPick_0=%%%plCustomer_Segment%%%&AccountEditForm.Name=%%%Name%%%&AccountEditForm.ZText_37=%%%stZone%%%&AccountEditForm.ZText_36=%%%stClass%%%&AccountEditForm.Parent Bill To Address.Bill To Country=%%%Bill_To_COUNTRY_Country%%%&AccountEditForm.ZPick_3=%%%plCustomer_Group%%%&AccountEditForm.Description=%%%Description%%%&AccountEditForm.ZPick_5=%%%plUS_GPOs%%&AccountEditForm.
However, I am not able to make it work for four remaining fields:
Address 1
City
ZIP
State
Any ideas?
Regards,
Søren

Soren, I have not been able to copy the address block fields either. Maybe someone can find a way.

Similar Messages

Help , how to auto create user account

Hi, guys,
i wanna to know how to auto create user account after use the suppliers' api to create supplier.
i didn't find out how to auto create user account by use ap_vendor_pub_pkg.create_vendor_contact procedure.
how to auto create the user account ?
if you know ,tell me ,pls
best Regards !
Edited by: wanjin on 2013-4-15 下午11:50

Hi Gareth，
I wanna create an Oracle E-business Suite use account ,but how to use fnd_user_pkg.createuser procedure to relation the AP suppliers , not employee suppliers.
the result like N:Purchasing Super User -->supplier-->Contact Directory --> create user
then use "Create User Account for this Contact" to create user account
Regards,
Wanjin

Auto created line item in J1inchln

Sap Gurus
while doing J1INCHLN extra line is creating for WCT liability account.
FS10n WCT liability account is showing credit balance of Rs 125000
while updating challan one extra line item in credit side is generating by system automatically for Rs 3150 and debit the Liability account, by crediting the Govt. as vendor account by 128150.
WCT liability A/C        Dr       128150
Govt. Vendor A/C      Cr       125000
WCT liability A/C       Cr         3150.Auto Created
Why this entry is generating Please suggest.
Pavan

Hi Pavan,
Check the Govt. Vendor master - withholding tax tab, whether any TDS payment related tax codes are assigned. If so remove them and run the transactions again.
Hope it helps

Groups/Roles ACI Procedures for Creating Accounts

Hello;
I am trying to determine the steps I need to perform in order to create a group/role, under "Groups"; "Groups" does not yet exist inside of my directory.
Inside of "Groups", I wish to create a container named "UserAdmins", for which users I make as members would be capable of creating accounts for other users.
In my current environment, in order to create user accounts, admins must be able to add/modify entries in:
1. People
2. group
3. auto.home
4. aliases
My questions, given the information below is:
A. Do my ACI's seem sound for my purposes?
B. How do I create a second ACI, similar to UserAdmins, but with the added ability of "deleting" entries as well as add and modify? (say called "SuperUserAdmins").
-----Create Groups---------------------
dn: ou=Groups, sub,dc=domain,dc=com
objectclass: top
objectclass: organizationalunit
ou: Groups
-----UserAdmins.aci--------------------
aci: (target="ldap:///dc=sub,dc=domain,dc=com") (targetattr =
"*")(version 3.0; acl "allow all Admin group"; allow(all) groupdn =
"ldap:///cn=UserAdmins,ou=Groups,dc=sub,dc=domain,dc=com";)
dn: ou=Groups, dc=sub,dc=domain,dc=com
objectclass: top
objectclass: organizationalunit
ou: Groups
------Initial add of Members to UserAdmins--------
dn: cn=UserAdmins, ou=Groups, dc=sub,dc=domain,dc=com
cn: UserAdmins
objectclass: top
objectclass: groupofuniquenames
ou: Groups
uniquemember: uid=smitha, ou=People, dc=sub,dc=domain,dc=com
uniquemember: uid=youngt, ou=People, dc=sub,dc=domain,dc=com
uniquemember: uid=weizerb, ou=People, dc=sub,dc=domain,dc=com

The last field is for the attribute to delegate. You can read about it here: https://technet.microsoft.com/en-us/library/cc772662%28v=ws.10%29.aspx
You can also refer to this for updating AdminSDHolder container: http://social.technet.microsoft.com/wiki/contents/articles/22331.adminsdholder-protected-groups-and-security-descriptor-propagator.aspx
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

Shopping without creating account

Hello,
One of our customers would like to allow customers (one time customers) doing shopping without creating account and log in to the portal. Do you have any idea is it possible ?
Thanks
Greg.

I know that Vision 33 has made a customization that does this, I would contact them to see if it is for sale to get around this for cheaper than custom coding it yourself. I believe what they did was have a program that auto-generates a user name and password as soon as the customer hits the checkout page.
James

PO CNV: Auto-Create POs from PUR Reqs generated by OM

Objective: Convert open sales orders and maintain the link to the purchase order for back to back and drop shipment sales orders?
Question: Is it possible to convert the sales orders first. Then run requisition import to create the purchase requisitions in the PO module. After the requisition lines are created, convert the purchase orders through the open interface table or an API by auto-creating the PO from the requisition lines? This would maintain the link between purchasing and order management.
If this is not possible, does anyone have any suggestions? Someone mentioned using BPAs (this assumes I can assign items to specific suppliers).
Any ideas are greatly appreciated.
Thanks

Hi,
After creating a PR, why you want to go thru open interface.
There is a standard functionality : AUTOCREATE, available , which will convert the PR to PO.
On PO Shipment level, you can view the SO number & Line Number also.
Please review the below link.
Oracle Applications - Functional: Business Flow of Drop Ship Order

Auto-create delivery for multiple sales orders

I would like to ask how to create auto-create 'single' delivery
for multiple sales order during release sales order in R11i.
It is found in my example during release sales order, multiple
sales orders fulfill release sales order criteria, a single pick
slip is generated but it is found that each sales order have
individual delivery with it. It will casue multiple pack slips
for a singles pick slip. Is it normal feature for auto-create
delivery, or any setup to solve it?
Thanks in advance.

Am not able to do Single Delivery for Muktiple sales orders
Have you searched the forum for this question as to why you were not able to generate ?? It could be due to multiple reasons. Please search the forum and update here what steps you have taken after taking the inputs from here, if the problem is still not resolved.
thanks
G. Lakshmipathi

HT1311 To create a new apple ID, if I sign out of the current Apple ID account, and then sign in with a newly created account, will I lose any songs or apps on my phone or computer that were downloaded from the old apple ID?

To create a new apple ID, if I sign out of the current Apple ID account, and then sign in with a newly created account, will I lose any songs or apps on my Iphone and Macbook Pro computer that were downloaded from the old apple ID?

No, you will not loose anything. However, if you ever need to update any of that previously purchased content, or re-download it, you will have to use the older AppleID. Purchases are permanently tied to the AppleID you use when making the purchase.

Event 0032 - To create Account Payable in FPCJ

Hi All,
I am working in Insurance module - FS CD , in transaction FPCJ. While posting documents by clicking on-account Postings,posting is made to a dummy account, we need to ensure this is balanced to zero i.e there is no balance remaining in the account.So in this case i need to add a additional posting on a account in order to balance the dummy account and add the offset entry to create the payable .
For this case, i copied the standard function module in the event 0032 and populated the table T_FKKOP_NEW with a additional account,but this did not help on clearing the dummy account. Please let me know if this situation could be handled in any other way.
Thanks and Regards,
Arundathi Veeraraghavan.

Hi Naresh,
I've already set the BP Vendor sync
After that i've created in the IMG an account assignment reference for my loan
In the transaction FBBP: application 0101
for the transaction type: 1110 (Nominal interest)
Payment transaction: X
I need to create:
40 Debit
31 Vendor
Is it possible to create accounting for the vendor?
Thanks,
Regards.
Adriana

Error when i create accounting

frist of all sorry if i put this message in wrong subject or wrong thread.this is my frist time in forum
dear all,
i use ebs r12 12.1.2 os Linux x86-64
when i create accounting i meet error this log :
Application Object Library: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
FNDWFBG module: Workflow Background Process
Current system time is 15-APR-2011 01:39:37
**Starts**15-APR-2011 01:39:37
**Ends**15-APR-2011 01:39:37
Start of log messages from FND_FILE
End of log messages from FND_FILE
Successfully resubmitted concurrent program FNDWFBG with request ID 450126 to start at 15-APR-2011 01:53:18 (ROUTINE=AFPSRS)
Executing request completion options...
Output is not being printed because:
The print option has been disabled for this report.
------------- 1) PRINT   -------------
Finished executing request completion options.
Concurrent request completed successfully
Current system time is 15-APR-2011 01:39:37
Subledger Accounting: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
XLAACCPB module: Create Accounting
Current system time is 16-JAN-2012 12:43:15
XDO Data Engine Version No: 5.6.3
Resp: 20639
Org ID : 81
Request ID: 450125
All Parameters: P_APPLICATION_ID=200:P_SOURCE_APPLICATION_ID=200:P_DUMMY=Y:P_LEDGER_ID=2023:P_PROCESS_CATEGORY_CODE=PAYMENTS:P_END_DATE="2012/01/10 00:00:00":P_CREATE_ACCOUNTING_FLAG=Y:P_DUMMY_PARAM_1=Y:P_ACCOUNTING_MODE=D:P_DUMMY_PARAM_2=:P_ERRORS_ONLY_FLAG=N:P_REPORT_STYLE=D:P_TRANSFER_TO_GL_FLAG=:P_DUMMY_PARAM_3=:P_POST_IN_GL_FLAG=:P_GL_BATCH_NAME=test11:P_MIN_PRECISION=:P_INCLUDE_ZERO_AMOUNT_LINES=N:P_REQUEST_ID=:P_ENTITY_ID=:P_SOURCE_APPLICATION_NAME=Payables:P_APPLICATION_NAME=Payables:P_LEDGER_NAME=SMI_PL:P_PROCESS_CATEGORY_NAME=Payments:P_CREATE_ACCOUNTING=Yes:P_ACCOUNTING_MODE_NAME=Draft:P_ERRORS_ONLY=No:P_ACCOUNTING_REPORT_LEVEL=Detail:P_TRANSFER_TO_GL=:P_POST_IN_GL=:P_INCLUDE_ZERO_AMT_LINES=No:P_VALUATION_METHOD_CODE=:P_SECURITY_INT_1=:P_SECURITY_INT_2=:P_SECURITY_INT_3=:P_SECURITY_CHAR_1=:P_SECURITY_CHAR_2=:P_SECURITY_CHAR_3=:P_CONC_REQUEST_ID=:P_INCLUDE_USER_TRX_ID_FLAG=N:P_INCLUDE_USER_TRX_IDENTIFIERS=No:DebugFlag=Y:P_USER_ID=1110
Data Template Code: XLAACCPB
Data Template Application Short Name: XLA
Debug Flag: Y
{P_ACCOUNTING_REPORT_LEVEL=Detail, P_DUMMY=Y, P_ACCOUNTING_MODE_NAME=Draft, P_ERRORS_ONLY_FLAG=N, P_REPORT_STYLE=D, P_GL_BATCH_NAME=test11, P_END_DATE=2012/01/10 00:00:00, P_SECURITY_INT_3=, P_SECURITY_INT_2=, P_SECURITY_INT_1=, P_VALUATION_METHOD_CODE=, P_POST_IN_GL=, P_TRANSFER_TO_GL=, P_TRANSFER_TO_GL_FLAG=, P_INCLUDE_USER_TRX_IDENTIFIERS=No, P_USER_ID=1110, P_PROCESS_CATEGORY_NAME=Payments, P_ERRORS_ONLY=No, P_DUMMY_PARAM_3=, P_SECURITY_CHAR_3=, P_DUMMY_PARAM_2=, P_SECURITY_CHAR_2=, P_DUMMY_PARAM_1=Y, P_SECURITY_CHAR_1=, P_ENTITY_ID=, P_PROCESS_CATEGORY_CODE=PAYMENTS, P_INCLUDE_ZERO_AMT_LINES=No, P_LEDGER_ID=2023, P_POST_IN_GL_FLAG=, P_APPLICATION_ID=200, P_INCLUDE_USER_TRX_ID_FLAG=N, P_APPLICATION_NAME=Payables, P_REQUEST_ID=, P_CONC_REQUEST_ID=, P_LEDGER_NAME=SMI_PL, P_SOURCE_APPLICATION_ID=200, P_CREATE_ACCOUNTING=Yes, P_CREATE_ACCOUNTING_FLAG=Y, P_MIN_PRECISION=, P_SOURCE_APPLICATION_NAME=Payables, P_INCLUDE_ZERO_AMOUNT_LINES=N, P_ACCOUNTING_MODE=D}
Calling XDO Data Engine...
[011612_124319140][][STATEMENT] oracle.jdbc.driver.OracleBlobInputStream@179f36b
[011612_124319242][][STATEMENT] Logger.init(): *** DEBUG MODE IS OFF. ***
[011612_124319244][][STATEMENT] DataTemplate.getTmpDir(): system-temp-dir property value from DATABASE: /usr/temp
[011612_124319246][][STATEMENT] Template parsing started...
[011612_124319389][][STATEMENT] Data Template ......
[011612_124319389][][STATEMENT] oracle.xml.parser.v2.XMLDocument@19fdbcb
[011612_124319525][][STATEMENT] Inside properties Parser...
[011612_124319525][][STATEMENT] db_fetch_size=20
[011612_124319526][][STATEMENT] Inside parameterParser...
[011612_124319527][][STATEMENT] Parameter:P_REQUEST_ID Default value:
[011612_124319527][][STATEMENT] Parameter:P_ENTITY_ID Default value:
[011612_124319527][][STATEMENT] Parameter:P_SOURCE_APPLICATION_ID Default value:
[011612_124319527][][STATEMENT] Parameter:P_SOURCE_APPLICATION_NAME Default value:
[011612_124319527][][STATEMENT] Parameter:P_APPLICATION_ID Default value:
[011612_124319527][][STATEMENT] Parameter:P_APPLICATION_NAME Default value:
[011612_124319527][][STATEMENT] Parameter:P_DUMMY Default value:
[011612_124319527][][STATEMENT] Parameter:P_LEDGER_ID Default value:
[011612_124319527][][STATEMENT] Parameter:P_LEDGER_NAME Default value:
[011612_124319527][][STATEMENT] Parameter:P_PROCESS_CATEGORY_CODE Default value:
[011612_124319528][][STATEMENT] Parameter:P_PROCESS_CATEGORY_NAME Default value:
[011612_124319528][][STATEMENT] Parameter:P_END_DATE Default value:
[011612_124319528][][STATEMENT] Parameter:P_CREATE_ACCOUNTING_FLAG Default value:
[011612_124319528][][STATEMENT] Parameter:P_CREATE_ACCOUNTING Default value:
[011612_124319528][][STATEMENT] Parameter:P_DUMMY_PARAM_1 Default value:
[011612_124319528][][STATEMENT] Parameter:P_ACCOUNTING_MODE Default value:
[011612_124319528][][STATEMENT] Parameter:P_DUMMY_PARAM_2 Default value:
[011612_124319528][][STATEMENT] Parameter:P_ERRORS_ONLY_FLAG Default value:
[011612_124319528][][STATEMENT] Parameter:P_REPORT_STYLE Default value:
[011612_124319528][][STATEMENT] Parameter:P_ACCOUNTING_MODE_NAME Default value:
[011612_124319528][][STATEMENT] Parameter:P_ERRORS_ONLY Default value:
[011612_124319528][][STATEMENT] Parameter:P_ACCOUNTING_REPORT_LEVEL Default value:
[011612_124319529][][STATEMENT] Parameter:P_TRANSFER_TO_GL_FLAG Default value:
[011612_124319529][][STATEMENT] Parameter:P_TRANSFER_TO_GL Default value:
[011612_124319529][][STATEMENT] Parameter:P_DUMMY_PARAM_3 Default value:
[011612_124319529][][STATEMENT] Parameter:P_POST_IN_GL_FLAG Default value:
[011612_124319529][][STATEMENT] Parameter:P_POST_IN_GL Default value:
[011612_124319529][][STATEMENT] Parameter:P_GL_BATCH_NAME Default value:
[011612_124319529][][STATEMENT] Parameter:P_MIN_PRECISION Default value:
[011612_124319529][][STATEMENT] Parameter:P_INCLUDE_ZERO_AMOUNT_LINES Default value:
[011612_124319529][][STATEMENT] Parameter:P_INCLUDE_ZERO_AMT_LINES Default value:
[011612_124319530][][STATEMENT] Parameter:P_VALUATION_METHOD_CODE Default value:
[011612_124319530][][STATEMENT] Parameter:P_SECURITY_INT_1 Default value:
[011612_124319530][][STATEMENT] Parameter:P_SECURITY_INT_2 Default value:
[011612_124319530][][STATEMENT] Parameter:P_SECURITY_INT_3 Default value:
[011612_124319530][][STATEMENT] Parameter:P_SECURITY_CHAR_1 Default value:
[011612_124319530][][STATEMENT] Parameter:P_SECURITY_CHAR_2 Default value:
[011612_124319530][][STATEMENT] Parameter:P_SECURITY_CHAR_3 Default value:
[011612_124319530][][STATEMENT] Parameter:P_CONC_REQUEST_ID Default value:
[011612_124319531][][STATEMENT] Parameter:P_INCLUDE_USER_TRX_ID_FLAG Default value:
[011612_124319531][][STATEMENT] Parameter:P_INCLUDE_USER_TRX_IDENTIFIERS Default value:
[011612_124319531][][STATEMENT] Parameter:P_USER_ID Default value:
[011612_124319531][][STATEMENT] Inside dataQueryParser...
[011612_124319535][][STATEMENT] Inside dataStructureParser...
[011612_124319540][][STATEMENT] Group ...report
[011612_124319541][][STATEMENT] Group ...APPLICATION
[011612_124319542][][STATEMENT] Group ...APPLICATION_FLAG
[011612_124319543][][STATEMENT] Group ...NO_ACTION_EVT
[011612_124319544][][STATEMENT] Group ...ACCT_PROG_ERRORS
[011612_124319545][][STATEMENT] Group ...EVENT_CLASS_S
[011612_124319545][][STATEMENT] Group ...LEDGER_S
[011612_124319546][][STATEMENT] Group ...BALANCE_TYPE_S
[011612_124319547][][STATEMENT] Group ...EVENT
[011612_124319548][][STATEMENT] Group ...AE_HEADERS
[011612_124319550][][STATEMENT] Group ...AE_LINES
[011612_124319551][][STATEMENT] Group ...AE_ERRORS
[011612_124319552][][STATEMENT] Group ...NO_ENTRY_EVENTS
[011612_124319553][][STATEMENT] Template parsing completed...
[011612_124319553][][STATEMENT] Setting Data Template
[011612_124319553][][STATEMENT] Setting JDBC Connection
[011612_124319576][][STATEMENT] Paramter :P_REQUEST_ID Value :
[011612_124319642][][STATEMENT] Paramter :P_ENTITY_ID Value :
[011612_124319642][][STATEMENT] Paramter :P_SOURCE_APPLICATION_ID Value :200
[011612_124319642][][STATEMENT] Paramter :P_SOURCE_APPLICATION_NAME Value :Payables
[011612_124319642][][STATEMENT] Paramter :P_APPLICATION_ID Value :200
[011612_124319642][][STATEMENT] Paramter :P_APPLICATION_NAME Value :Payables
[011612_124319642][][STATEMENT] Paramter :P_DUMMY Value :Y
[011612_124319642][][STATEMENT] Paramter :P_LEDGER_ID Value :2023
[011612_124319642][][STATEMENT] Paramter :P_LEDGER_NAME Value :SMI_PL
[011612_124319643][][STATEMENT] Paramter :P_PROCESS_CATEGORY_CODE Value :PAYMENTS
[011612_124319643][][STATEMENT] Paramter :P_PROCESS_CATEGORY_NAME Value :Payments
[011612_124319658][][STATEMENT] Paramter :P_END_DATE Value :2012/01/10 00:00:00
[011612_124319658][][STATEMENT] Paramter :P_CREATE_ACCOUNTING_FLAG Value :Y
[011612_124319658][][STATEMENT] Paramter :P_CREATE_ACCOUNTING Value :Yes
[011612_124319658][][STATEMENT] Paramter :P_DUMMY_PARAM_1 Value :Y
[011612_124319658][][STATEMENT] Paramter :P_ACCOUNTING_MODE Value :D
[011612_124319658][][STATEMENT] Paramter :P_DUMMY_PARAM_2 Value :
[011612_124319658][][STATEMENT] Paramter :P_ERRORS_ONLY_FLAG Value :N
[011612_124319658][][STATEMENT] Paramter :P_REPORT_STYLE Value :D
[011612_124319658][][STATEMENT] Paramter :P_ACCOUNTING_MODE_NAME Value :Draft
[011612_124319658][][STATEMENT] Paramter :P_ERRORS_ONLY Value :No
[011612_124319658][][STATEMENT] Paramter :P_ACCOUNTING_REPORT_LEVEL Value :Detail
[011612_124319658][][STATEMENT] Paramter :P_TRANSFER_TO_GL_FLAG Value :
[011612_124319658][][STATEMENT] Paramter :P_TRANSFER_TO_GL Value :
[011612_124319659][][STATEMENT] Paramter :P_DUMMY_PARAM_3 Value :
[011612_124319659][][STATEMENT] Paramter :P_POST_IN_GL_FLAG Value :
[011612_124319659][][STATEMENT] Paramter :P_POST_IN_GL Value :
[011612_124319659][][STATEMENT] Paramter :P_GL_BATCH_NAME Value :test11
[011612_124319750][][STATEMENT] Paramter :P_MIN_PRECISION Value :
[011612_124319751][][STATEMENT] Paramter :P_INCLUDE_ZERO_AMOUNT_LINES Value :N
[011612_124319751][][STATEMENT] Paramter :P_INCLUDE_ZERO_AMT_LINES Value :No
[011612_124319751][][STATEMENT] Paramter :P_VALUATION_METHOD_CODE Value :
[011612_124319772][][STATEMENT] Paramter :P_SECURITY_INT_1 Value :
[011612_124319837][][STATEMENT] Paramter :P_SECURITY_INT_2 Value :
[011612_124319891][][STATEMENT] Paramter :P_SECURITY_INT_3 Value :
[011612_124319891][][STATEMENT] Paramter :P_SECURITY_CHAR_1 Value :
[011612_124319891][][STATEMENT] Paramter :P_SECURITY_CHAR_2 Value :
[011612_124319892][][STATEMENT] Paramter :P_SECURITY_CHAR_3 Value :
[011612_124319958][][STATEMENT] Paramter :P_CONC_REQUEST_ID Value :
[011612_124319958][][STATEMENT] Paramter :P_INCLUDE_USER_TRX_ID_FLAG Value :N
[011612_124319958][][STATEMENT] Paramter :P_INCLUDE_USER_TRX_IDENTIFIERS Value :No
[011612_124319958][][STATEMENT] Paramter :P_USER_ID Value :1110
[011612_124319958][][STATEMENT] Setting Parameters
[011612_124319958][][STATEMENT] Setting Parameters
[011612_124319960][][STATEMENT] Start process Data
[011612_124319960][][STATEMENT] Process Data ...
[011612_124319966][][STATEMENT] Executing data triggers...
[011612_124319966][][STATEMENT] BEGIN
XLA_CREATE_ACCT_RPT_PVT.P_REQUEST_ID := :P_REQUEST_ID ;
XLA_CREATE_ACCT_RPT_PVT.P_ENTITY_ID := :P_ENTITY_ID ;
XLA_CREATE_ACCT_RPT_PVT.P_SOURCE_APPLICATION_ID := :P_SOURCE_APPLICATION_ID ;
XLA_CREATE_ACCT_RPT_PVT.P_SOURCE_APPLICATION_NAME := :P_SOURCE_APPLICATION_NAME ;
XLA_CREATE_ACCT_RPT_PVT.P_APPLICATION_ID := :P_APPLICATION_ID ;
XLA_CREATE_ACCT_RPT_PVT.P_APPLICATION_NAME := :P_APPLICATION_NAME ;
XLA_CREATE_ACCT_RPT_PVT.P_DUMMY := :P_DUMMY ;
XLA_CREATE_ACCT_RPT_PVT.P_LEDGER_ID := :P_LEDGER_ID ;
XLA_CREATE_ACCT_RPT_PVT.P_LEDGER_NAME := :P_LEDGER_NAME ;
XLA_CREATE_ACCT_RPT_PVT.P_PROCESS_CATEGORY_CODE := :P_PROCESS_CATEGORY_CODE ;
XLA_CREATE_ACCT_RPT_PVT.P_PROCESS_CATEGORY_NAME := :P_PROCESS_CATEGORY_NAME ;
XLA_CREATE_ACCT_RPT_PVT.P_END_DATE := :P_END_DATE ;
XLA_CREATE_ACCT_RPT_PVT.P_CREATE_ACCOUNTING_FLAG := :P_CREATE_ACCOUNTING_FLAG ;
XLA_CREATE_ACCT_RPT_PVT.P_CREATE_ACCOUNTING := :P_CREATE_ACCOUNTING ;
XLA_CREATE_ACCT_RPT_PVT.P_DUMMY_PARAM_1 := :P_DUMMY_PARAM_1 ;
XLA_CREATE_ACCT_RPT_PVT.P_ACCOUNTING_MODE := :P_ACCOUNTING_MODE ;
XLA_CREATE_ACCT_RPT_PVT.P_DUMMY_PARAM_2 := :P_DUMMY_PARAM_2 ;
XLA_CREATE_ACCT_RPT_PVT.P_ERRORS_ONLY_FLAG := :P_ERRORS_ONLY_FLAG ;
XLA_CREATE_ACCT_RPT_PVT.P_REPORT_STYLE := :P_REPORT_STYLE ;
XLA_CREATE_ACCT_RPT_PVT.P_ACCOUNTING_MODE_NAME := :P_ACCOUNTING_MODE_NAME ;
XLA_CREATE_ACCT_RPT_PVT.P_ERRORS_ONLY := :P_ERRORS_ONLY ;
XLA_CREATE_ACCT_RPT_PVT.P_ACCOUNTING_REPORT_LEVEL := :P_ACCOUNTING_REPORT_LEVEL ;
XLA_CREATE_ACCT_RPT_PVT.P_TRANSFER_TO_GL_FLAG := :P_TRANSFER_TO_GL_FLAG ;
XLA_CREATE_ACCT_RPT_PVT.P_TRANSFER_TO_GL := :P_TRANSFER_TO_GL ;
XLA_CREATE_ACCT_RPT_PVT.P_DUMMY_PARAM_3 := :P_DUMMY_PARAM_3 ;
XLA_CREATE_ACCT_RPT_PVT.P_POST_IN_GL_FLAG := :P_POST_IN_GL_FLAG ;
XLA_CREATE_ACCT_RPT_PVT.P_POST_IN_GL := :P_POST_IN_GL ;
XLA_CREATE_ACCT_RPT_PVT.P_GL_BATCH_NAME := :P_GL_BATCH_NAME ;
XLA_CREATE_ACCT_RPT_PVT.P_MIN_PRECISION := :P_MIN_PRECISION ;
XLA_CREATE_ACCT_RPT_PVT.P_INCLUDE_ZERO_AMOUNT_LINES := :P_INCLUDE_ZERO_AMOUNT_LINES ;
XLA_CREATE_ACCT_RPT_PVT.P_INCLUDE_ZERO_AMT_LINES := :P_INCLUDE_ZERO_AMT_LINES ;
XLA_CREATE_ACCT_RPT_PVT.P_VALUATION_METHOD_CODE := :P_VALUATION_METHOD_CODE ;
XLA_CREATE_ACCT_RPT_PVT.P_SECURITY_INT_1 := :P_SECURITY_INT_1 ;
XLA_CREATE_ACCT_RPT_PVT.P_SECURITY_INT_2 := :P_SECURITY_INT_2 ;
XLA_CREATE_ACCT_RPT_PVT.P_SECURITY_INT_3 := :P_SECURITY_INT_3 ;
XLA_CREATE_ACCT_RPT_PVT.P_SECURITY_CHAR_1 := :P_SECURITY_CHAR_1 ;
XLA_CREATE_ACCT_RPT_PVT.P_SECURITY_CHAR_2 := :P_SECURITY_CHAR_2 ;
XLA_CREATE_ACCT_RPT_PVT.P_SECURITY_CHAR_3 := :P_SECURITY_CHAR_3 ;
XLA_CREATE_ACCT_RPT_PVT.P_CONC_REQUEST_ID := :P_CONC_REQUEST_ID ;
XLA_CREATE_ACCT_RPT_PVT.P_INCLUDE_USER_TRX_ID_FLAG := :P_INCLUDE_USER_TRX_ID_FLAG ;
XLA_CREATE_ACCT_RPT_PVT.P_INCLUDE_USER_TRX_IDENTIFIERS := :P_INCLUDE_USER_TRX_IDENTIFIERS ;
XLA_CREATE_ACCT_RPT_PVT.P_USER_ID := :P_USER_ID ;
:XDO_OUT_PARAMETER := 1;
END;
[011612_124319966][][STATEMENT] 1:null :
[011612_124319966][][STATEMENT] 2:null :
[011612_124319967][][STATEMENT] 3:200 :
[011612_124319967][][STATEMENT] 4:Payables :
[011612_124319967][][STATEMENT] 5:200 :
[011612_124319967][][STATEMENT] 6:Payables :
[011612_124319967][][STATEMENT] 7:Y :
[011612_124319967][][STATEMENT] 8:2023 :
[011612_124319967][][STATEMENT] 9:SMI_PL :
[011612_124319967][][STATEMENT] 10:PAYMENTS :
[011612_124319967][][STATEMENT] 11:Payments :
[011612_124319968][][STATEMENT] 12:2012-01-10 00:00:00.0 :
[011612_124319968][][STATEMENT] 13:Y :
[011612_124319968][][STATEMENT] 14:Yes :
[011612_124319968][][STATEMENT] 15:Y :
[011612_124319968][][STATEMENT] 16:D :
[011612_124319968][][STATEMENT] 17: :
[011612_124319968][][STATEMENT] 18:N :
[011612_124319968][][STATEMENT] 19:D :
[011612_124319968][][STATEMENT] 20:Draft :
[011612_124319968][][STATEMENT] 21:No :
[011612_124319968][][STATEMENT] 22:Detail :
[011612_124319968][][STATEMENT] 23: :
[011612_124319968][][STATEMENT] 24: :
[011612_124319968][][STATEMENT] 25: :
[011612_124319968][][STATEMENT] 26: :
[011612_124319968][][STATEMENT] 27: :
[011612_124319968][][STATEMENT] 28:test11 :
[011612_124319969][][STATEMENT] 29:null :
[011612_124319969][][STATEMENT] 30:N :
[011612_124319969][][STATEMENT] 31:No :
[011612_124319969][][STATEMENT] 32: :
[011612_124319969][][STATEMENT] 33:null :
[011612_124319969][][STATEMENT] 34:null :
[011612_124319969][][STATEMENT] 35:null :
[011612_124319969][][STATEMENT] 36: :
[011612_124319969][][STATEMENT] 37: :
[011612_124319969][][STATEMENT] 38: :
[011612_124319969][][STATEMENT] 39:null :
[011612_124319969][][STATEMENT] 40:N :
[011612_124319969][][STATEMENT] 41:No :
[011612_124319969][][STATEMENT] 42:1110 :
[011612_124319971][][STATEMENT] Executing data triggers...
[011612_124319971][][STATEMENT] Declare
l_flag Boolean;
BEGIN
l_flag := XLA_CREATE_ACCT_RPT_PVT.BeforeReport ;
if (l_flag) then
:XDO_OUT_PARAMETER := 1;
end if;
end;
[011612_124319994][][EXCEPTION] SQLException encounter while executing data trigger....
java.sql.SQLException: ORA-20001: -: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla_create_acct_rpt_pvt.BeforeReport . ORA-20001: -: XLA-95103: An internal error occurred.
ORA-06512: at "APPS.APP_EXCEPTION", line 72
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 110
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 289
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 162
ORA-06512: at "APPS.XLA_CREATE_ACCT_RPT_PVT", line 275
ORA-06512: at line 4
     at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
     at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1034)
     at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:191)
     at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:950)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1225)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3387)
     at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3488)
     at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:3857)
     at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1374)
     at oracle.apps.xdo.dataengine.XMLPGEN.executeTriggers(XMLPGEN.java:650)
     at oracle.apps.xdo.dataengine.XMLPGEN.processData(XMLPGEN.java:263)
     at oracle.apps.xdo.dataengine.XMLPGEN.processXML(XMLPGEN.java:215)
     at oracle.apps.xdo.dataengine.XMLPGEN.writeXML(XMLPGEN.java:254)
     at oracle.apps.xdo.dataengine.DataProcessor.processDataStructre(DataProcessor.java:390)
     at oracle.apps.xdo.dataengine.DataProcessor.processData(DataProcessor.java:355)
     at oracle.apps.xdo.oa.util.DataTemplate.processData(DataTemplate.java:334)
     at oracle.apps.xdo.oa.cp.JCP4XDODataEngine.runProgram(JCP4XDODataEngine.java:294)
     at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
Oracle error 20100: java.sql.SQLException: ORA-20100: Error: FND_FILE failure. Unable to create file, o0010400.tmp in the directory, /usr/tmp.
You will find more information in the request log.
ORA-06512: at "APPS.FND_FILE", line 417
ORA-06512: at "APPS.FND_FILE", line 526
ORA-06512: at "APPS.FND_CONCURRENT", line 1328
ORA-06512: at line 1
has been detected in FND_CONCURRENT.SET_INTERIM_STATUS.+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
End of log messages from FND_FILE
Executing request completion options...
------------- 1) PUBLISH -------------
Beginning post-processing of request 450125 on node ORAAPPS at 16-JAN-2012 12:43:20.
Post-processing of request 450125 failed at 16-JAN-2012 12:43:21 with the error message:
One or more post-processing actions failed. Consult the OPP service log for details.
Finished executing request completion options.
Concurrent request completed
Current system time is 16-JAN-2012 12:43:21
anyone have same problem and already solving ??
Thanks,
Mahardika

[011612_124319994][][EXCEPTION] SQLException encounter while executing data trigger....
java.sql.SQLException: ORA-20001: -: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla_create_acct_rpt_pvt.BeforeReport . ORA-20001: -: XLA-95103: An internal error occurred.
ORA-06512: at "APPS.APP_EXCEPTION", line 72
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 110
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 289
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 162
ORA-06512: at "APPS.XLA_CREATE_ACCT_RPT_PVT", line 275
ORA-06512: at line 4Please make sure you have no invalid objects.
Please also see these docs.
R12: Ap Invoice Online Accounting with Final Post Ends With Errors ORA-20001 XLA-95103 [ID 853424.1]
FAACCPB Create Accounting Internal Error xla_create_acct_rpt_pvt.BeforeReport [ID 783493.1]
CSTCRACC Create Accounting Err ORA-20001 Xla-95103 Internal Error Occurred ORA-01400 [ID 1309124.1]
CSTCRACC - Create Accounting - Cost Management Completes With Errors: java.sql.SQLException, ORA-20001, XLA-95103 [ID 1252703.1]
Create Accounting Concurrent Program Errors - ORA-20001 XLA-95103 [ID 1392267.1]
Create Accounting Error Due To Invalid Package Apps.Ap_payment_extract_details_v [ID 1366269.1]
------------- 1) PUBLISH -------------
Beginning post-processing of request 450125 on node ORAAPPS at 16-JAN-2012 12:43:20.
Post-processing of request 450125 failed at 16-JAN-2012 12:43:21 with the error message:
One or more post-processing actions failed. Consult the OPP service log for details.
Also check OPP log file ($APPLCSF/$APPLLOG/FNDOPP* file).
Thanks,
Hussein

Create Accounting when completed in warning the output is coming in XML

Hello to all,
I am having APPS version 12.1.3 OS version OEL 5.5
my problem is that when i am running Create Accounting concurrent request if it completes in warning the output (view output) is coming in XML in browser where as if its completing normal then the output appears correctly as expected, the output type for create accounting concurrent program is XML.
Please advise / guide me
thanks

Please find below log file details
==============================================================================================
Start of log messages from FND_FILE
06-OCT-2011 10:36:08 - Beginning of the Report
06-OCT-2011 10:36:08 - Starting of the Parent Thread
Starting main program for the source application = 200
06-OCT-2011 10:36:08 - Dynamic conditions built
06-OCT-2011 10:36:08 - Event Applications Determined
06-OCT-2011 10:36:08 - Security Context Set
06-OCT-2011 10:36:08 - Session Identifier Set
06-OCT-2011 10:36:08 - Setup for the ledger and Event applications Read
06-OCT-2011 10:36:08 - executing preaccounting hook
event key = 10-426334
06-OCT-2011 10:36:08 - preaccounting hook executed successfully
06-OCT-2011 10:36:08 - Pre-Accounting steps performed
06-OCT-2011 10:36:08 - Queue Created = XLA.XLA_426334_DOC_Q
06-OCT-2011 10:36:08 - Queue Created = XLA.XLA_426334_COMP_Q
06-OCT-2011 10:36:08 - Queue Started = XLA.XLA_426334_DOC_Q
06-OCT-2011 10:36:08 - Queue Started = XLA.XLA_426334_COMP_Q
06-OCT-2011 10:36:08 - Global Context Initialized
06-OCT-2011 10:36:08 - Calling sequencing batch_init
06-OCT-2011 10:36:08 - Returned from sequencing batch_init
06-OCT-2011 10:36:08 - Begin enqueue
06-OCT-2011 10:36:08 - Ready to Enqueue documents in the queue
06-OCT-2011 10:36:08 - Spawning unit processors
06-OCT-2011 10:36:08 - Unit processors spawned
06-OCT-2011 10:36:36 - Ready to Enqueue documents in the queue
06-OCT-2011 10:36:36 - Ready to Enqueue documents in the queue
06-OCT-2011 10:36:36 - Ready to Enqueue documents in the queue
06-OCT-2011 10:36:36 - Ready to Enqueue documents in the queue
06-OCT-2011 10:36:36 - Enqueueing completed
06-OCT-2011 10:36:36 - Waiting for Unit Processor requests to complete
06-OCT-2011 10:37:06 - Child Threads completed
06-OCT-2011 10:37:06 - Global Context cleared
06-OCT-2011 10:37:06 - Queue stopped = XLA.XLA_426334_DOC_Q
06-OCT-2011 10:37:06 - Queue stopped = XLA.XLA_426334_COMP_Q
06-OCT-2011 10:37:06 - Queue dropped = XLA.XLA_426334_DOC_Q
06-OCT-2011 10:37:06 - Queue dropped = XLA.XLA_426334_COMP_Q
06-OCT-2011 10:37:06 - Calling sequencing batch_exit
06-OCT-2011 10:37:06 - Returned from sequencing batch_exit
06-OCT-2011 10:37:06 - Executed post-accounting routine
06-OCT-2011 10:37:06 - Accounting Program completed successfully
06-OCT-2011 10:37:06 - executing postaccounting hook
event key = 10-426334
06-OCT-2011 10:37:06 - postaccounting hook executed successfully
- Accounting Time = 58.73 secs
- Transfer Time = 0 secs
06-OCT-2011 10:37:06 - End of the Report
End of log messages from FND_FILE
Executing request completion options...
Output file size:
1920
------------- 1) PUBLISH -------------
Beginning post-processing of request 426334 on node M at 06-OCT-2011 10:37:06.
Post-processing of request 426334 failed at 06-OCT-2011 10:39:06 with the error message:
The Output Post-processor is running but has not picked up this request.
No further attempts will be made to post-process this request, and the request will be marked
with Warning status.
Setting the profile option Concurrent: OPP Response Timeout to a higher value may be necessary.
------------- 2) PRINT -------------
Not printing the output of this request because post-processing failed.
Finished executing request completion options.
Concurrent request completed
Current system time is 06-OCT-2011 10:39:06
Edited by: hassanksa on Oct 8, 2011 8:15 AM
Edited by: hassanksa on Oct 8, 2011 8:16 AM

I try to create my Account ID....and i don't understand why i have to put payment? before my friend create Account ID don't have to put payment they still can create account ID... and now i buy iphone but i don't have credit card that mind i can't not do

Dear
I try to create my Account ID....and i don't understand why i have to put payment? before my friend create Account ID don't have to put payment they still can create account ID... and now i buy iphone but i don't have credit card that mind i can't not do it

Hi,
This Link explains how to Set Up an Account ID... without a credit card...
http://support.apple.com/kb/HT2534
Hope it helps,
Cheers,

Error creating accounting document for a credit note

Hi All,
I am facing an issue while creating an accounting document for the credit note created.
The scenario is as follows:
Created a credit memo --> created credit note --> create accounting document
While creating accounting document, i'm getting an error message as 'The G/L account XXXXXXXX requires an assignement to CO object'.
Please let me know why i'm getting this error and how to overcome this issue.
Thanks,
Anil Kumar

While creating accounting document,
i'm getting an error message
First of all, I am not clear on your above statement as in normal circumstances, once you generate a credit memo, in bacground an accounting document will also be generated.
In your case, I believe while saving the credit memo, system throws the error to maintain CO object in which case, do the following:-
Go to TCode KA02 enter the controlling area, give the G/L acoount No and click on Master data tab. There select "Default Acc Assgmnt" tab and enter Cost centr and save.
Next Go to FS00, input the G/L Account and click on Edit Cost Element on top. There click on Basic Data and for the field CElem category, maintain the required numeric value. Now select the tab Default Acct Assgnmt and there maintain the required cost center and save.
thanks
G. Lakshmipathi

Cancel billing doc (S1) is not creating Accounting document

Hi,
I have cancelled F2 billing document with cancel billing type S1. But for that cancel billign doc S1 is still in open status only and it is not creating accounting document..
I tried to release to accounting but it is showing error like " Document type is not defined"..
Please any guess on this..
regards
sankar

Hi sankar
I am sure you might be aware of this but just to reiterate
When you cancel documents in Logistics Invoice Verification, the document line items are not automatically cleared in Financial Accounting. We recommend that you periodically clear such items (using daily background jobs, for example).
Kalpesh

Unable to create Accounting document for my Outgoing excise Invoice

Dear All,
I am implementing sales from Factory. I am unable to creat accounting document for my Outgoing excise invoice. When I click the Utilization button, The excise invoice type is selected Deemed.
1. How to control which Which Excise invoice type should be selected in J1IIN.
2. For Deemed exports will system not genererate Accounting document for Excise Invoice?
3. Where to view the excise invoice document types (Like Billing and order types)
Thanks & Regards

For deemed export sales,
-Accounting documents will not get generated. (ref: Excise Acct Determination in CIN settings, you will not find Excise Tranraction type:ARE3 for which G/L account will not be assigned)
-Excise Invoice type will be automatically triggered based on configuration : Excise Group / Series Group detetermination.
- For Deemed Exports , only Quantity will get updated in RG1, but not the value. thats the reason, accounting document will not get generated.
- This excise invoice is created, for - to update the RG1 registry / ARE3 creation.
hope it clears
regards,

Auto create account

Similar Messages

Maybe you are looking for