Accounting No not Created For Sales Orders when Processed thru Credit cards

Hi Experts,
I was able to successfully post FI document through Billing document in SD.
The Problem is encountered when a Sales Order is created
for Credit Card customers.
When the sales order is created the credit card information we are prompted with an error message Payment terms is a required field for G/L Acc so and so...
The payment terms field in the posting key 01 is marked required and the same field for the reconcilation account is optional. However this config has not created any problem for the Non credit card sales orders.
If any one has faced the same problem. Please help me out in this issue.
Thanks,
Chaitanya

Hi Friends,
Please refer SAP OSS Note 119047.
In the OSS Note they have mentioned..
Pass the payment terms to the field
xaccit-zterm = '0001'. in the User Exit.
Program : LV60BF0C,
Customer Function '002'.
Include File ZXVVFU02.
SE 37:- EXIT_SAPLV60B_002
Still I don't understand why SAP doesn't support payment terms for Credit Card. But when a Sales Order is created without credit card the field xaccit-zterm has a value.
Thanks,
Chaitanya K

Similar Messages

BAPI_NETWORK_COMP_ADD     Component assignment not intended for sales order

Dear,
I have problem when I use the function:
CALL FUNCTION 'BAPI_NETWORK_COMP_ADD'
    EXPORTING
      number           = number
    IMPORTING
      return           = return
    TABLES
      i_components_add = i_components_add
      e_message_table = e_message_table.
I have inserted only these values in the structure i_components_add:
ACTIVITY_TYPE_PUR_RESV__ITEM_NR____MATERIAL_________PLANT___ENTRY_QTY___ITEM_CAT
108--8101TAH052000110025.460--
L
108--8204RAVBLA098SL0111002.000--
L
108--83034R000000011004.160--
L
but the result is wrong
e_message_table:
METHOD--C--
32
OBJECT_TYPE--C--
32
INTERNAL_OBJECT_ID---C--
90
EXTERNAL_OBJECT_ID--C90-----0108 0010 1TAH052000 1100
MESSAGE_ID--C20-----CNIF_MAT
MESSAGE_NUMBER--C3--
1
MESSAGE_TYPE--C1--
E
MESSAGE_TEXT--C72--
Component assignment not intended for sales order or project stock
Very kind for one answer of yours to this problem...
Thanks & Regards,
Marco Echino.
Edited by: Marco Echino on Sep 8, 2011 12:16 PM

Hi Marco,
I believe this is a Functional Issue rather than a Technical one. If you could speak to the Functional Concultant or pass this data via manual transaction, you will get the error details.
It's just that the data passed to the BAPI is either incorrect or incomplete. You can also refer the Function Module Documentation for tips.
Regards,
Pranav.

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

How settlement rule will be created for Sales order with cost object

Dear Experts,
We are using product cost by sales order with valuated stock. In addition we are not using COPA
We also consume some materials at sales order level and at the end of month we want to do the result analysis and settlement for the same amount. In this case can any on explain how system will behave regarding settlement of sales order cost and what entries will get pass in the system.
In our case we have done below activities...
we have created sales order,
All production order activities completed till final GRN including month end activities
Material consumption against sales order
Result analysis executed
At the time of sales order settlement, system throwing error (Sender doesn't have valid receiver, please create settlement rule for sender object)
Then i checked in sales order there sales order settlement rule not defined.
I guess this settlement rule need be generated by system automatically. If not, please let me know the process of it.

HI kishore
the reason is that sale order always carry the revenue and production order and production period carry the cost .
cost you can settle to the Material and even management want to be settle the cost to material only in production order OR period
but in sales order when u sell the product it carry the revenue not the cost and management want see and analysis based on profitability segment are profit center level .
Prerequisites
If CO-PA is active, the system generates a settlement rule when you create the sales order. The settlement rule determines whether data is settled to other objects or other areas in Controlling. In accordance with this settlement rule, the relevant data is settled to CO-PA.
If CO-PA is not active, create a settlement rule. This settlement rule that you create manually normally contains a G/L account as a receiver (such as 399999). You can also settle costs and revenues or results analysis data to objects with revenue.
You can also settle the cost of sales calculated in results analysis to a fixed asset or a cost center. To do this, you must add to the allocation structure the results analysis cost elements under which the cost of sales is updated to the order.
The settlement rule includes a distribution rule for the sales order item. The distribution rule is made up of a settlement receiver, a settlement share, and a settlement type:
The settlement receiver (such as profitability segment or G/L account) specifies the object to which the actual costs and revenue of the sales order item are settled. The settlement receiver can be proposed through the settlement profile.
The settlement share defines the percentage or the equivalence numbers used to distribute the costs to the individual settlement receivers. The settlement share for sales order items is usually 100%. A settlement share of 100% is preset in the system.
The settlement type specifies full settlement of the sales order item. This ensures that all the data on the sales order is available for results analysis.
Settlement still takes place in each period. The revenues and the cost of sales are transferred to CO-PA by period, and the work in process and the reserves are transferred to FI.

Customer GL Account Updates by Creating a Sales Order

Dear all,
I would like to know detailed information about customer GL Account updates based on Sales Order creation.
We have a POS system, there we are creating Sales Orders for the customers.
As per my knowledge by creating a sales order system is performing the following jobs.
Debiting Customer Account
Crediting Sales Account.
Please suggest me that my understanding is right or not.
What else job is performed with regards to financial accounts for the customer.
Where can I see these updations at each level starting from Sales Order creation, Delivery and Invoice.
Please educate to get a clear idea of the process. your suggestions will be highly appreciated.
Thank you
Raghu Ram

Hi,
there will no accounting entry at sales order creation.
Here is the sd cycle:
sales order no accounting effect
goods deleivery to customer
COGS a/c dr
to stock
Billing to customer
customer a/c dr
to sales revenue
Hope this is clear
pls assign points if it was
Thanks
Vamsi

Credit Management- KRML Output not generated for Sales Order ( v.v.u.)

<u>Credit Management - Credit control check at Sales order Level</u>
While saving the Sales order,which failed the Credit check ( As per Automatic Credit Check Settings), there is no output generated for output type KRML, for Partner Fn KB/KM. Normally,If credit check is NOK, then while saving the sales order, an internal mail is sent to the SAP office inbox of the Credit representative ( KB/KM). There is option for an external send also. The problem faced by us is that, the mail is not going in SAP Office inbox in quality server , it is going in developement server.We checked in table NAST that the Output for KRML (o/p type) is not generated. Kindly suggest what could be the reason.
Regards
Sunil Kumar

Dear Mr. Gauravjit,
Thank you for your valuable reply.
At the Extra-Output-Header-edit-goto-det analysis ,system give message as KRML o/p is not generated since Requirement 009 is not being fulfilled. But we checked the VBUK-CMGST = B is satisfied. Still the o/p not generated!
Also , in VV11 we maintained the Cond Records. Still the o/p is not coming.
The output is coming in Devlopment , but in Quality the output is not coming.
Can anybody please help !
P.S. I am colleague of Mr. Sunil Kumar, and reply on behalf of him.
With Best Regards,
Kaustuv

FM to get purchase requisiton created for Sales order in APO

Hello experts,
I want to know is there any FM or BAPI exists in APO to get Purchase requisiton created for a sales order created in R/3 using sales order number? and FM or BAPI to get the sales order config data. if the mapping of sales order and purchase requisition is in Table, Please mention those tables also.
Many thanks,
Senthil

Hi,
Please see the below link for useful SCM BAPIs....
http://wiki.sdn.sap.com/wiki/display/SCM/SCM+BAPIs
For sales order config data, BAPI_SLSRVAPS_GETLIST2 is available.
Regards,
Saurabh

HT1420 my account is not available even tho i added a new credit card

My account is not available even tho i added a new credit card

This is an open forum, not Adobe support... you need Adobe staff support to help
Adobe contact information - http://helpx.adobe.com/contact.html
-Select your product and what you need help with
-Click on the blue box "Still need help? Contact us"
-or by telephone http://helpx.adobe.com/x-productkb/global/phone-support-orders.html

Import order not creating internal sales orders for some orgs

Hi,
We are getting one issue in UAT instance. The details are as below -
1. Created Sales Orders in all 7 orgs.
2. Ran ASCP plan
3. planned orders got auto released in all orgs.
4. Corresponding Internal requisitions got created in all orgs.
5. Ran 'Create Internal Orders' from each org.
6. Ran 'Order Import' from BE org as all the IR's were sourced from BE as per sourcing rules.
7. Issue is that out of 7 orgs, in 2 orgs, DK and SE, the internal sales orders didn't get created and order import gave error. I am attaching the error log below.
For other 5 orgs, ISO got created successfully and we performed picking/shipping and receiving as well for these 5 orgs.
Any help will be most welcome.
error log is -
Order Import Concurrent Program
Concurrent Program Parameters
Validate Only: N
Order Source: 10
Order Ref:
Sold To Org Id:
Sold To Org:
Change Sequence:
Performance Parameter: Y
Trim Blanks: N
Operation:
Number of Instances: 0
Debug Level: 0
Request Id: 6891
Org Id: 2453
Failed to perform Action Request BOOK_ORDER
Failed to perform Action Request BOOK_ORDER
Failed to perform Action Request BOOK_ORDER
No. of orders found: 2
No. of orders imported: 0
No. of orders failed: 2
Source/Order/Seq/Line Message
10/1046001536//2 User-Defined Exception in Package OE_SCHEDULE_UTIL Procedure Load_Results_from_rec
10/1046001536//2 ATP Process resulted in no data
10/1046001536//2 User-Defined Exception in Package OE_SCHEDULE_UTIL Procedure Load_Results_from_tbl
10/1046001538//2 User-Defined Exception in Package OE_SCHEDULE_UTIL Procedure Load_Results_from_rec
10/1046001538//2 ATP Process resulted in no data
10/1046001538//2 User-Defined Exception in Package OE_SCHEDULE_UTIL Procedure Load_Results_from_tbl
End of Order Import Concurrent Program

Try running the Order import from a responsibility where the profile "OM: Override ATP flag" is set to YES at that responsibility level..

Accounting douctment not generating during sales order builling.

Hi
When i am doing billing to sales order XX Accounting douctment is not generating.
t code VF01
Error like
No billing documents were generated. See log.
and during goods delive vl01n and post goods issues.
every thing is working fine.
please help me.
thanks
kareem

Hi ,
I have did what u have informed me.
but i found some thing from it.
i created sales order va01. did sales order cost estimate here.
and did mdo2 for finised product.
and did md04 for raw material , create po for it and did migo for it.
and created production order for finished goods did confirmation for it through co11n.
did goods receiot fot that production order .
here i have calcualted variance as no taget cost exist here it has comapare target cost as 0
and calcualted actual cost as variace 100% of it and settle it to raw materials.
i did deliver and billing for that sales order.
but when i have settle it form sales order to copa through va88.
i got only revenue is updated here i am not getting cogm and cogm break up.
when i have went and saw in ke24 actual line items.
raw material is updated which is flown to kks2 calculation.
thanks
kareem

Archive is not happening for Sales Order

Hello Friends,
I want to archive sales order but it is not happening.
Following is scenario.
I have completed sales order cycle till amount posting
va01-vl01n-PGI-vf01-f-28
and document flow has shown it is done but still when i am running report S3VBAKPTS it shows document can not be archived billing document is not complete.
Help me for the same
Regards
BHavesh

Hi,
once the subsequenat document created for a sales order, you cannot archive that sales order.
reagrds,
Sumith

Accounting document not created for PGI

Dear All,
I have done PGI for Delivery document.
The movement type is 601 and Special Stock indicator is E (Order 0n Hand).
While PGI material document has been created but accounting document has not created.
Waiting for your valuable suggestion
Thanks & Regards,
Ratish

Accounting / Materil Document in PGI:
These settings are pre configured by the SAP, Accounting document is generated based on the following combination-
Valuation Class in the Material Master + Account Modifier + Transaction Event = GL Account
These account modifier is assigned to Movement type settings in Transaction OBYC of Accounting and these Account modifier is determined based on the Movement type availabe in Delivery.
Material Document is generated based on the number range assigned on the combination of Documen type(WL) + Transaction code.

Accounting document not created for the billing document in CIN

Hi Experts,
I have made conditon records for BED, CESS, Edu Cess and VAT. I hve defined the accounts in both excise transactions and VKOA Settings even then the accounting document is not getting created. I am getting the following error.
No account is specified in item 0000001003
Message no. F5670
Help to solve the above
Thanks in Advance

Open the document in VF02 / VF03, go to Environment -> Acct. Determination Analysis -> Revenue Accounts. (You can also press CtrlShiftF12). There check for the item no. 1003. You'll find no account has been determined for this item through any procedure.
In the right pane, it will also give other details like CoA, Sales Org etc (as per your access sequence) which it tried to find the account for. Assign an account for that combination in VKOA and then try to release the doc for accounting. It should work if you have assigned correctly.
Ravi.

Copied layout is not working for Sales order item assinment block

Hi Experts,
I copied the standard componet BT115IT_SLS/items view layout with custom role configuration key and worked fine.
I have added one more field to the item view with the same configuration and saved .When I opended the sales order in the WEB UI , The item assigment block is displaying with complete BTADMINI context fileds and This is the issue.
I have seen configured fields only in the personalization and I have downloaded the items assigment block data to Execl.In the Execl sheet I can able to see the configured fields (availble fileds in the configuration tab in component workbemch) data only.
But Items assignment block is displaying all the fileds (taking from the context node BTADMINI).
I have deleted existing customer configuration and again copied from the standard layout.But I got the same issue.
I have wriiten some code in the ON_NEW_FOCUS and commented the code.Still it not working.
Please help me , where I have done the mistake and provide me some inputs.
Thanks,
Venkky

Hi Experts,
Solved isuues myself.
The problem is inconsistency of BTAdminI context node . I have deleted the view enhancement and again enhanced the view .I copied the layout with customer role key and dispalyed expected layout.
Thanks,
Venkky

How to find out the list of Production orders created for sales orders

Dear All,
Our company wants to generate a report for a List of Materials sold out in a particular Product Hierarchy. Along with that we want to know the list of Production orders created for the sales orders.
How to identify the production orders which are created based on Sales orders.
Kindly suggest.
Regards,
Mullairaja

Check these threads
[Sale Order & Production Order|Sale Order & Production Order;
[Re: Linking Production Order against a Sale Order MRP run|Linking Production Order against a Sale Order MRP run;
thanks
G. Lakshmipathi

Accounting No not Created For Sales Orders when Processed thru Credit cards

Similar Messages

Maybe you are looking for