Text Determination at Opportunity creation dependent to the Sales Orga

Hello experts,
we try to define a text determination for opportunities dependent to the sales organisation. That means we have a text type calles e.g. "Sales Orga TEXT". In an opportunity at creation time, the user's sales orga will be determined for the opp. Dependent to this sales orga we want to determine different content for the text type "Sales Orga TEXT".
I've created a function module for this issue. I don't know how i can get the sales orga of an opp at creation time. Is there a structure which is available at this time? Or how can I get this info?
Somebody any ideas?
Thanks
Abbas

Use function module CRM_ORDER_READ and get the organization details from the output structures for ORG ET_ORGMAN or more so use the function module CRM_ORGMAN_READ_OW and get the org details.
You need the header guid of the transaction.

Similar Messages

Possibility of addition creation time in the sales order over view screen

Hi,
Is there a possibility of adding the creation time in the sales order overview screen in VA01/2/3.
thank you

hi,
this is to inform you that,
contact your ABAPER for this is to find out if there any possibility making time field mandatory if it is there in Standard SAP. there in VBAK table i am able to see VBAK - ERZET
or
if it is not available then you need to go for field exit.
hope this helps.
balajia
Edited by: balaji timmampalli achari on Nov 30, 2010 6:11 AM

Hide the characteristics grouping buttons depending on the sales order type

Hi Gurus,
I am trying to find a way to hide a characteristics grouping button (CU50) whenever a certain sales order type is issued.
A condition was created that states that a certain characteristic will be invisible for the user depending on the sales order type chosen for that case. The characteristic is located inside a char. grouping button.
I would like to know id there is a way to hide the button while the characteristic is hidden as well, just to avoid showing a button which is empty.
If It is of any help, here is the condition created to turn the char invisible:
$SELF.INVISIBLE = 'N01017_E'.
*if not $self.N01017_E specified
Thanks in advance.
Kind regards.

Hi!
Sounds like you need a line-triggered output (with a message, which displays all lines of the order).
Do you have problems to create a new output type?
Regards,
Christian

Org Data Determination in Opportunity

Dear All,
While Opportunity Creation, after entering the sales prospect, contact person and employee responsible and Organizational data have to be determined automatically. To achieve this what configuration settings I have to make in SPRO.
Please educate me in this scenario. Your help will be highly appreciated.
Thank you

Hi Raghu
This is based on the org determination rules which are assigned to the transaction types.
These rules are defined to pick up the responsible agent/org based on two criteria
1. Based on attributes
2. Based on responsibilities
3. Both of the above
Incase when the org is to be determined based on the attributes, then the attributes of the BP like the Countyr, Postal code are matched to the same attributes of the orgs that you have maintianed in the system and the matching orgs are available for chosing.
<b>Based on the responsibility</b>:- Incase you want the BP to be serviced based on his importance you chose agents based on the Responsibility. Eg:- If you want the Gold Card Members to be treated by different set of org than the normal customers, you can chose this rule to maintian it.
Incase you have maintained both the rules, then the union of all the orgs determined by these rules will be available in the pop.
The path to maintain these rules is
IMG> CRM> Master Data> Org Mangement> Define Rules
and then these rules need to be assigned to a profile which contains the rules to determine both sales and service orgs is done using the path
IMG>CRM>Master Data> Org Management> Define profile
and then these profiles are assgined to the transaction type using the path IMG>CRM> Transactions> Basic Settings> Define transaction types
Hope this would help.
Regards,
Rekha Dadwal
You gain a point for every point that you reward. So reward helpful answers generously

Customization steps of the text determination processes

Can anybody anybody tell the customization steps of the text determination processes (transaction codes: VOTXN and SO10) of the header of the sales documents step by step in a detailed manner?
Thanks in advance.

Hi Hikmet,
In a business relationship, it is essential that business partners exchange information throughout the logistics chain. In sales and distribution, this exchange of information is supported by texts in master records and documents. You can maintain these texts for one particular customer or define them so that they can be used more flexibly.
Texts can be used in many areas of sales and distribution:
Sales notes for customers
Sales texts for materials
Explanations in order confirmations
Shipping instructions in deliveries
http://help.sap.com/saphelp_erp2005vp/helpdata/en/38/9e9263a1f611d199ad0000e8a5bd28/frameset.htm
reward points if it helps u
with regards
Rajesh
RMD
Posts: 381
Questions: 24
Registered: 1/10/07
Forum points: 690
   Re: Text determination
Posted: Apr 5, 2007 12:42 PM    in response to: raju pusapati       Reply      E-mail this post
Hi,
In a business relationship, it is essential that business partners exchange information throughout the logistics chain. In sales and distribution, this exchange of information is supported by texts in master records and documents. You can maintain these texts for one particular customer or define them so that they can be used more flexibly.
Texts can be used in many areas of sales and distribution:
Sales notes for customers
Sales texts for materials
Explanations in order confirmations
Shipping instructions in deliveries
You can define as many text types as you require (sales texts, shipping texts, internal notes, supplement texts etc.) for master records and documents.
You can take the settings for the texts from Sales and Distribution Customizing under Text control.
Features
You store the texts that are to serve as information carriers in the system and in the output in the customer master record, the material master record, and in the sales and distribution documents. In addition the following processing and control functions are supported:
Texts are proposed from the master records in the sales and distribution documents, if you have made the appropriate setting.
Texts can be copied from a reference sales and distribution document into another sales and distribution document (e.g. from an inquiry into a sales order or from an order into a delivery).
The copying of texts can be made language dependent, if required.
You can change copied texts.
You can integrate standard texts into the sales and distribution documents.
If you want to use texts more than once, you can enter these texts as standard texts and include them in the master record or document texts. If you define standard texts, they are included in the sales and distribution forms when they are issued.
Some standard texts to which you can refer in the sales and distribution documents have been defined in the standard version of the SAP R/3 System.
Notes on Entering Text
You can use standard texts to give notes to the employee entering an sales and distribution document regarding the information he should include in specific header or item texts and the sequence in which he should do it. For example, by including a standard text such as a header note in the sales document, you can make sure that the employee specifies in the first line whether the customer has taken advantage of a sales promotion in his purchase order and in the second line, how (newspaper, radio etc.) he found out about the promotion.
Proposals from the Master Records
The standard text above must first of all be created and then included in a text in the customer master. You can define in Customizing whether this text is automatically proposed from the customer master record in the header note of the document header when you create a sales document.
Standard texts can be proposed in the documents at header and item level in the same way from the material master record.
Create
To create a standard text, proceed as follows:
Select Tools ® SAPscript ® Standard text on the main menu screen.
Enter a name for the text to be created in the field Text name, the indicator ST in the field Text-ID, and the abbreviation for the language in which you want to create the text in the field Language.
Select Create/Change.
You switch to the SAPscript editor. If no standard text has been created with this name, the following message is displayed: Text stands for the language indicator with which you control the language of the standard text. The line in which you make these entries must have the formatting key /: (paragraph format for a command line) in the format column.
Calling Up At the Time of Issue
In Customizing any number of standard texts can be included in the definition of a sales and distribution forms. The texts then appear in the appropriate place in the form when each output is issued.
Further Information
You will find additional information on the SAPscript editor and on INCLUDEs as well as examples online in the hypertext system under the text module name STXD_ED. Proceed as follows:
Select Tools ® Hypertext ® Structures on the main menu screen.
Enter the text module name in the Structure field and in the Language field the abbreviation for the required language.
Select Structure ® Display.
You reach the Display Structure screen.
Place the cursor on the entry that you want to read and select Goto ® Document ® Read.
The content of the text module is displayed on the screen.
Select Back to return to the initial screen.
Also Visit-
http://help.sap.com/saphelp_47x200/helpdata/en/90/758534c960a134e10000009b38f83b/frameset.htm
REWARD IF U FINDS THIS AS USEFUL....
Regds
MM

Default the opportunity currency at the time of opportunity creation

Hello,
How to default the opportunity currency at the time of opportunity creation. At the time lead conversion it is defaulted according to lead currency but when creating a new lead it is not working fine.
Thanks
Subbu

Hi CRMWise,
You can use the JoinField Value function for this.
To default it with the user currency, you can pick the currency from User level.
For new record creation you can put the validation ion the default value and check the post default check box so once you save the record it will be automatically defaulted.
For modified record, you can have a workflow with an update action which can again use the Join Field value function, once you will modify the record this workflow will trigger and update the currency field.
Syntx for JoinFieldValue is
JoinFieldValue('<User>',[<OwnerId>],'<EMailAddr>')
Hope you get the point.
Thanks,
Mayank

Text determination for different languages

how to set up text determination of different languages based on the customer country location.What is the configuration?
Thanks for your help,
Andy

hi,
it is not related to customer.
it depends on LOG ON LANGUAGE.
if you have not given any thing it will be in ENGLISH.
hope this clears your issue
balajia

TEXT DETERMINATION & PARTNER DET

HI,
CAN YOU ALL TELL ME STEPS OF TEXT DETERMINATION & PARTNER DET. IN SAP 4.7 EE ?
RAJARSHI

HI.,
In a business relationship, it is essential that business partners exchange information throughout the logistics chain. In sales and distribution, this exchange of information is supported by texts in master records and documents. You can maintain these texts for one particular customer or define them so that they can be used more flexibly.
Texts can be used in many areas of sales and distribution:
Sales notes for customers
Sales texts for materials
Explanations in order confirmations
Shipping instructions in deliveries
You can define as many text types as you require (sales texts, shipping texts, internal notes, supplement texts etc.) for master records and documents.
You can take the settings for the texts from Sales and Distribution Customizing under Text control.
Features
You store the texts that are to serve as information carriers in the system and in the output in the customer master record, the material master record, and in the sales and distribution documents. In addition the following processing and control functions are supported:
Texts are proposed from the master records in the sales and distribution documents, if you have made the appropriate setting.
Texts can be copied from a reference sales and distribution document into another sales and distribution document (e.g. from an inquiry into a sales order or from an order into a delivery).
The copying of texts can be made language dependent, if required.
You can change copied texts.
You can integrate standard texts into the sales and distribution documents.
If you want to use texts more than once, you can enter these texts as standard texts and include them in the master record or document texts. If you define standard texts, they are included in the sales and distribution forms when they are issued.
Some standard texts to which you can refer in the sales and distribution documents have been defined in the standard version of the SAP R/3 System.
Notes on Entering Text
You can use standard texts to give notes to the employee entering an sales and distribution document regarding the information he should include in specific header or item texts and the sequence in which he should do it. For example, by including a standard text such as a header note in the sales document, you can make sure that the employee specifies in the first line whether the customer has taken advantage of a sales promotion in his purchase order and in the second line, how (newspaper, radio etc.) he found out about the promotion.
Proposals from the Master Records
The standard text above must first of all be created and then included in a text in the customer master. You can define in Customizing whether this text is automatically proposed from the customer master record in the header note of the document header when you create a sales document.
Standard texts can be proposed in the documents at header and item level in the same way from the material master record.
Create
To create a standard text, proceed as follows:
Select Tools ® SAPscript ® Standard text on the main menu screen.
Enter a name for the text to be created in the field Text name, the indicator ST in the field Text-ID, and the abbreviation for the language in which you want to create the text in the field Language.
Select Create/Change.
You switch to the SAPscript editor. If no standard text has been created with this name, the following message is displayed: Text stands for the language indicator with which you control the language of the standard text. The line in which you make these entries must have the formatting key /: (paragraph format for a command line) in the format column.
Calling Up At the Time of Issue
In Customizing any number of standard texts can be included in the definition of a sales and distribution forms. The texts then appear in the appropriate place in the form when each output is issued.
Further Information
You will find additional information on the SAPscript editor and on INCLUDEs as well as examples online in the hypertext system under the text module name STXD_ED. Proceed as follows:
Select Tools ® Hypertext ® Structures on the main menu screen.
Enter the text module name in the Structure field and in the Language field the abbreviation for the required language.
Select Structure ® Display.
You reach the Display Structure screen.
Place the cursor on the entry that you want to read and select Goto ® Document ® Read.
The content of the text module is displayed on the screen.
Select Back to return to the initial screen.
http://help.sap.com/saphelp_47x200/helpdata/en/90/758534c960a134e10000009b38f83b/frameset.htm
REWARD if helpfull
Thanks & Regards
Narayana

Text determination & Output

Hi,
We have configured txt determination in Customer master in general data & Sales area data individually. We have assigned text procedure to the account group.
I have also maintained text types, access seq and procedure for the sales document (Header). In access sequnce we have assigned the text id's which we have created for sales area data and central text so as to get the text determined in sales document header (OR)
In sales order, system determines the text for only one objct which ever is maintained in the top row of access sequence.
So what i presumed is, my access sequence is not able to search other ids, RIGHT ?
Is there any exclusive indicator ??
I am also unable to see the same text in output copy of order.
Regards,
Venksys.

Hi,
For the text to be seen in the output ask your APAP consultant to include functinon module READ_TEXT in the smart form code.
Hope this will help.
Regards,
Sharan

Text determination for business partneres

Hi
can any one provided me step by step process of text determination for business partner level
Many thanks
vinay

Hi Vinay
First U need to Define the Text Type for the Text determination for Business Partners.
Follow the Below Path
1)Img-Crm Basicfunctions-Textmanagment-Define Text objects and text types-
select text Object but000 and click on create- Give text id and description and save the text type
2)then u have to add the text type to the procedure
Define text determination procedure --select the text object but000 click on procedure and click on definition of procedure- go to new entries and add ur new type and save. ur text type will be reflected in the business partner.

Opportunity-like Info on the Account Page

For one of our user groups, using the Opportunity page doesn't make sense to track volumen/pipeline since actual applications/transactions don't come out of their direct work. So instead, we have set up their Account layout to include things like "volume", "sales stage ", "anticipated close date", "probability", and "expected volume".
Can you build logic so:
1. the probability changes depending on the sales stage?
2. the expected volume field is auto-filled based on the volume and probability?
I'd like to know if this is possible, and if so, how?!
Thanks in advance.
Rachel

RAZ,
You would need to use "When a record is modifed" workflows for this and it would only work on one at a time. That is:
Record has Sales Stage A and Probability 10%
Expected Volumne = volume X 10
Record changes sales stage to B
Workflow A will update the probability to 20% BUT
Workflow B will calculate the Expected volume as volume x 10.
The next time the record is saved Workflow B will calculate as volume x20
The workflows to update fields run 'before save' the probability is not actually updated until the save is processed so workflow B has to use the original value.
Hope this explains it so you understand it. Maybe someone else has another solution.
cheers
Alex

Text determination - sale order item text to be copied to delivery item tex

hi,
I have defined a text type and assigned to the text determination procedure and assigned those to the relevant item categories in the sales order item
How cn i configure the system so that the delivery item text should copy the same text from the sales order item to the delivery item.
Appreciate your help on this.
Thanks
keshini

Dear keshini,
To copy the sales order item text to the delivery document item text
-->You do the text determination for the sales order item and delivery item also through VOTXN transaction,
-->Define and maintain same TextId's in the sales order item text procedure and delivery item text procedure ,
-->Maintain the access sequence ,in the delivery item text procedure access sequence you put the Text Object as VBBK for that delivery itemText ID.
-->Assign the access sequence to the item text ID.
I hope this will help you,
Regards,
Murali.

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.

Country for the sales organization

Hi,
I need to associate a country to each one of the sales organization I have created in BW. What I don't know is whether there is any navigational attribute associated or I have to create a characteristic and give the value depending on the sales organization?
Can anybody help me?
Thanks in advance.
Regards.

Hi David,
As per your requirement, you may create an attribute of type Nav/Display.
Choose it based on your reporting requirement.
if you need Country to display only as property then you can make Display Attr or else if you need any furthur analysis based on Country like if you need your report to be grouped based on country then you need to make country as Nav attr of Sales Org.
Hope this helps.
Regards,
Naveen Kencha

How to retrieve invoice details from the sales order .. urgent..

hi,
i am retrieving vbak-vbeln with this i should retreive invoice details
how to relate vbak with abrk table
i have vbak -vbeln,erdat,VBAK- VKORG,VBAK-KUNNR,VBAK-VTWEG,VBAK- SPART.
its urgent..

Hi
U can see the sales order number in VBRP table, fields:
VBRP-AUBEL and VBRP-AUPOS.
But if u have the sales order number it's better to use VBFA table.
SELECT * FROM VBFA WHERE VBELV = VBAK-VBELN
AND VBTYP_N = 'M'
SELECT SINGLE * VBRK WHERE VBELN = VBFA-VBELN.
IF SY-SUBRC = 0.
WRITE: 'Bill number:', VBRK-VBELN.
ENDIF.
ENDSELECT.
U have to make sure to use the right document type:
M = Invoice
N = Invoice cancellation
So the bill type depends on the sales order type
Max

Text Determination at Opportunity creation dependent to the Sales Orga

Similar Messages

Maybe you are looking for