To populate condition in the sale order or a scenario in the USER Exit

Hi Experts,
I want to write the code in the USER EXIT to add a condition type in the Sale order when the ship-to-party address is changed in the transaction level from the address maintained in the Master data,
So can anyone let me know is there any function module or how will i populate condition type.
I found that the internal table XKOMV contains all the condition types.
Thanks,
Prem

i saw the answer provided by u, i was pleased to find the answered way, so i writing back to u regarding my requirements.
my requirement.
while creating sale order, before entering the screen 4001 where we enter sold to party and material and order quantity, i need to populate these fields from my exit.
i am able to populate the sold to party field from the exist EXIT_SAPMV45A_002 and
INCLUDE ZXVVAU04 .
in the same fashion i need to populate my material filed.
how do i do it

Similar Messages

VAT /CST% manually in the sales order,not getting copied to the Invoice

Dear Friends,
If I change the VAT /CST% manually in the sales order,its not getting copied to the Invoice
Thanks
Ivy

Dear Friends,
Thanks for your valuable inputs....
I have maintained the condition record for the combination of delivery plant region and the customer region.......assigned dummy tax code against the Tax condition...therefore I think there wont be any problem in posting billing doc to accounting doc.
There are different combinations,where sometimes the user is liable for 2% CST ....sometimes 4%CST... but I am able to pick one tax value say 12.5% CST across and maintained the tax condition types - manual entry has priority, as allowed the user to change the value manullay as per the user requirement ....
Now if i change the Tax condition value in the sales order ,the same is not reflecting in the Invoice....this also is applying from contract to a sales order...
Please advice me accordingly...
Thanks
Ivy

How to get know the Sales Order IDOC#, if I know the created Sales Order#?

Hi Experts,
Let me know that, How to get know the IODC #, if I know the Sales Order#?
Scenario is that, sales order(say 12345678) was created from Inbound EDI. I also Know the MATERIAL too.
So, How to pull the associated Inbound ORDERS idoc, which is created this Sales order-12345678?
Is it from EDID4 table? or EDIDC? or any thing else?
reples r appreciated.
thanq
Edited by: SAP ABAPer on Sep 8, 2008 5:29 AM

Hello
This can be done much easier using fm SREL_GET_NEXT_NEIGHBORS:
Input:
OBJECT-OBJKEY = <number of sales order> " with leading zeros!!!
OBJECT-OBJTYPE = 'BUS2032'
MAX_HOPS = '01'
Result:
NEIGHBORS-OBJKEY = <IDoc number with leading zeros>
NEIGHBORS-OBJTYPE = 'IDOC'
NEIGHBORS-ROLETYPE = 'INIDOC'.
Regards
Uwe

Filling the Sales Order Header - Source for filling the dropdown boxes

Hi,
I am trying to design the User Interface for Creation of sales order using the WebDynpro's. I want to know, what are all those BAPI's i need to use to fill the following drop down boxes.
1. Order Type
2. Sales Organization
3. Distribution Channel
4. Division
As i am new to ABAP., and i am from Java background, i dont know much about the BAPIs used to get the above data.
Could anyone let me know the source to fill those dropdown boxes. Thanks in advance.
Thanks,
Raghavendra

Ah,my bad.
Hmmm,i haven't found a BAPI's for filling all your dropdown-boxes with the valid values.
What about using the FM "RFC_READ_TABLE" to read the values for your drowdown-boxes.(only if you don't want to write a Z*-Function).
For examlpe for the dropdownbox "Sales Orgs",you can can start this FM for the table TVKOT.
Is that a possilbe solution for you?
Greetings
Frank Brackmann

Maximum Quantity restriction in the sales order?

Hi All
We need to make restriction of maximum order QTY with UOM in sales order key combination of sales organization wise / site wise / distribution Channel wise
While qty is entered for an article in sales order for which maximum sales order qty is maintained in some field (Article master or any other possible field)-, system has to check if the ordered quantity is greater than maximum sales order qty then should display error message and will not allow to process further
Hope the same is clear.
Regards,
C S Javali

hi
there is no standard functionality available to set the maximum limit for a material in the sales order.
You can try using user exit userexit_save_document_prepare in include MV45AFZZ.
You may need to use Z-table to enter the maximum value for sales organization / site / distribution Channel / material

How to hide the Condition types in item condition screen in Sales Order ?

Hi Experts,
We got new requirement from the Client. Pricing Condition types are ZZBG, ZPBG, ZPBA, ZFSG, ZBDG and ZBHG part in Pricing Procedure. These condition types have Condition records. These need to be hidden in Item conditions screen in Sales Order but other status of the conditions remain unchanged. Pleas provide me the solution earliest How this we can achieve in a best way.
Best Regards,
Srikith

Hi Srikanth,
You can achieve this using CONDITION EXCLUSION.
Maintain Condition exclusion for first condition type its Exclude the condition types which are below to that.
You must set a condition exclusion indicator for the price. You can do this in two ways:
If you want to set the condition exclusion indicator a follows then you specify it:
1..for all condition records of a condition type (e.g. with condition type PR00) when defining a condition type in SD Customizing
2.for an individual condition record (e.g. only for material 4711) in the detail screen of a condition record (in the Condition exclusion field)
Hope this will helps you
Dasaradha

Condition populated twice in the item conditions in the sales order

Hi,
We are creating the sales order through .csv flat file. The program calls the relevant BAPI which creates the sales order. It also fills the amount from the file for the manual condition type YNET in the pricing procedure. YNET is defaulted automatically in the sales order. But maintaining value is not mandatory.
The problem is in sales order, YNET is displayed twice in the item conditions.
One YNET with no value and another YNET with value which we passed through file.
Any suggestions how we can get only one YNET in the item conditions in the sales order or how the value from our file can be added against the YNET in the pricing procedure with showing another YNET in the item conditions in the sales order
Thanks in advance,

Hi Ramakrishnan,
Thanks for your reply. Its a manual condition type. No condition records maintained.
Thanks,
Ram
Original thread:
Hi,
We are creating the sales order through .csv flat file. The program calls the relevant BAPI which creates the sales order. It also fills the amount from the file for the manual condition type YNET in the pricing procedure. YNET is defaulted automatically in the sales order. But maintaining value is not mandatory.
The problem is in sales order, YNET is displayed twice in the item conditions.
One YNET with no value and another YNET with value which we passed through file.
Any suggestions how we can get only one YNET in the item conditions in the sales order or how the value from our file can be added against the YNET in the pricing procedure without showing another YNET in the item conditions in the sales order
Thanks in advance,

Free Goods not appearing in the Sales Order

Hi,
I have created the condition record for Exclusive free goods for a material. However when i create a sales order with the same material, the free goods materials is not appearing.
I did a Free goods Analysis in the sales order and when i checked the field values, I found that for a particular access sequence it says "Access not made ( initialized field)"
Please help.
Thanks.

Hi,
This error usually happens when we donot maintain any of the fields in the access sequence that we use.For Eg., if your access sequence is Sales Org/Dist Channel/Mat group and if you fail to maintain your condition record with the same sequence,you will get this error.Please maintain the condition record with the respective access sequence and you will not get this error.Please try and confirm.
(Also in the above example even if you maintain condition record and didnot maintain material group in the materisl master you will get this error.So check all the possibilities and confirm.)
Regards,
Phani Prasad.

System resets the sales order item price changes after save in VA02.

Hi All,
We have implemented automatic credit control at sales order level.
System is blocking the sales order once saved in VA01.
But if I do any changes in prices at item level in VA02 and save before credit releasing the sales order then system agian reset to the original prices from pricing condition records.
Can any body tell me why this is happening? I should able to change the sales order prices manually before releasing the sales order credit block. Is it possible?
Regards,
Kartheek.

Like Lakshmipathi said, you should be able to change the prices in the order even if the order is under credit limit block.
Please check the condition types which are being changed . In the condition type definition( T Code V/06) for the field Manual Changes - the value should be either "Manual entry has priority" or "....should allow to change manually...".
Also in your pricing procedure ( T Code V/08) , against your pricing procedure , please select the value for pricing type as ..."copy manual conditions and redetermine others".
Hope this helps
Regards
Sai

Can we change the net value in the conditons of the sales order?

Hello:
I have below scenario:
Sales order:
Material           A
PR01 (Price condition)               98 USD
ZADD (Discount condition)        to be calculated by SAP R3 system (?%)
Net price                                    80 USD (expected)
Due to the net value field can't be changed in the system, we have to maintain the discount rate, but we expect the R3 system can calculate the discount rate automatically.
My questions are:
1. How can I input the net price?(Should I have to maintain a value discount condition type?).
2. How to attach or include the discount rate(which will be calculated by the SAP R3 system) in the sales order?
Can anybody share the relevant solutions?
Thanks,
Don

Hi,
Maybe, my question is not clear.
I know on how to maintain the conditions.
I want to maintain a final price condition, and also the discount rate will be shown in the sales order.
discount rate= ( List Price 98- Final price 80) / List Price 98
Or
I want to maintain a value discount condition,and also need the discount rate will be shown in the sales order.
discount rate = value of the value discount condition 18 / List price 98
The discount rate will be shown in the sales order and the discount amount will be posted to the GL account.
Thanks&Regards,
Don

Condition types in Sales order creation process

Hi Friends...
While creating the sales order with BAPI,
What is the condition type i have to pass for pricing procedure...
There many condition types for my pricing procedure, which one o have to select...
Some of them are mannual, and other reuired, which one I have to pass?
I want the information related to this condition types.., as here no SD consultant availble for me.
Sales order creation, Line item error
Thanks,
Naveen.I

Hi Friends...
Please let me know is it mandatory to give condtion type while creating the sales order...?
I am using BAPI_SALESORDER_CREATEFROMDAT2 to create my sales order...
http://www.sap-img.com/abap/bapi-salesorder-createfromdat2.htm
Thanks,
Naveen.I

Discount Condition type in sales order screen

Hi Experts,
I have a requirement like ,While the creation of Sales order ,we need to add discount for each line item on the main sales order screen ,for that i need an extra field near to order quantity field,and it must be updated at the pricing procedure too for the corresponding line item.Please show me some light on how i can accomplish this.
Thank you all in advance

Hanumant,
In the sales order screen and in at the top - right corner of item details screen there is "Configuration" tab click it, it is using standard settings we can create customised setting too. Similarly we have under the conditions tab you can ask your ABAPer to check through th screen and create new one.
The price condiion type is picking from structure KOMV - KSCHL for condition type you can add fields just check with your Abaper.
Regards
Sathya

User Exit in the Sales order create BAPI

Hi,
Can some one help me in telling if there exists a user exit for the BAPI '/AFS/BAPI_SALESORDER_CREATE'.
This is urgent. So, pls. throw some light on this.
Thanks in advance.

Hi
User Exits In Sales Document Processing
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.

How-to extend the Sales Order with the Project ID?

Hello ByD Community,
My problem is the following:
I want to add an extension field to the Sales Order Header, which would be the Project ID assigned to this Sales Order.
My use case only involve one Project ID per Sales Order, and the task will be the same from a Line Item to another. So I can only use the GetFirst() to retrieve only the first Line Item.
Past week, I asked a similar question for the Purchase Orders and I succeeded to do it after a hint from Dan!
As for the Purchase Order, I thought the Project Assignment was built through the SalesOrder.Item.ItemAccountingCodingBlockDistribution.AccountingCodingBlockAssignment.ProjectReference, but it seems that it is different.
So as soon as I try to check if this Association IsSet() it just returns me that it is not!
I succeeded to bluntly push the TaskUUID in my Extension field for testing purpose, without any check and verification, but not the Project ID neither with good validations.
I also tried to see with the SalesItem Association instead of the Item Node, but it is the same. Any time I try a different check it returns me the N/A for my field, which is my last condition if the association is not set! What is driving me crazy is that you have the Project ID is shown on the top of the Sales Order, but I just cannot find how to retrieve it in the Studio!!!
Here is my sample code in my After-Modify event (I also tried with a On-Save) where the ProjectIDSalesOrder is my extension field in the Cloud Solution:
import ABSL;
if (this.Item.GetFirst().ItemAccountingCodingBlockDistribution.IsSet())
if (this.SalesItem.GetFirst().ItemProduct.ProductCategoryHierarchyProductCategoryIDKey.ProductCategoryInternalID.Matches("130"))
this.ProjectIDSalesOrder = this.SalesItem.GetFirst().ItemServiceTerms.ProjectTaskUUID.content.ToString();
/*what I need actually is : this.ProjectIDSalesOrder = this.Item.ItemAccountingCodingBlockDistribution.AccountingCodingBlockAssignment.GetFirst().ProjectReference.ProjectID.content;*/
else {this.ProjectIDSalesOrder = "No project assigned";}
else {this.ProjectIDSalesOrder = "N/A";}
If anybody could help me on this, it would be greatly appreciated.
Thank you community!
Best regards.
Jacques-Antoine

Hello all,
To follow up on this issue, I found that a QueryByElements is available in the SalesOrderOverview node. And we can Query the SalesOrder by ProjectID.
Fine! However, we cannot retrieve the ProjectID. It is never proposed as a result in the Query. We can query againt a ProjectID but not retrieve it.
As the ItemAccountingblockDistribution association seems to never be set, we can't retrieve the ProjectID from it neither.
I will post an incident to see if the ProjectID can be released as an entity in the SalesOrderOverview. QueryByElements results, so as to be able to use it.
Thanks for your attention.
Jacques-Antoine

Creation of Billing with reference to the Sales Order

Dear Friends,
I need your suggestion for the following scenario.
Client wants to create the Billing Document with reference to the Sales order.I mean when he is entering sales Order while creating the billing document ,the system should generate the billing document only for the delivered quantity.
e.g sales order is created for 100 Tons.And there are 5 delivery documents for 50 Tons.(Still the Sales order is open).
Now when billing document is created with reference to the sales order ( Not with reference to the Delivery Document) it should create the billing document only for these five deliveries.
Is it possible? If yes,how?
Thanks in advance.
Regards,
Shrikant

Hi Murali,
Currently client has software where he enters only Sales Order no and their software creates the billing for the delivery document for this Sales Order.
Here client does not want to enter multiple delivery document nos if any.He wants to enter only Sales Order no.
Regards,
Shrikant

To populate condition in the sale order or a scenario in the USER Exit

Similar Messages

Maybe you are looking for