Sales information view in PS

In PS standard function, how can I see sales information?
sales information is customer name, contract value, contract date, contract type, payment term, billing plan etc.
regards,

In which report you are looking for these information. Please let us know. IN some of the PS report give you Sales view information that also very much preliminarily level, You get get the same with help of dynamic selection of report,
But the information you are asking, that much detailed level information you will not get from PS in any of Std. PS reports. You need to for some development.
WIth Regards
NItin P.

Similar Messages

Maximum lines set on Sales Order view

Hi All,
This is happening with all sales orders with more than 8 items, where the rest of the items are not seen in the sale order after creation and save. For example 15 different type of material were sold to customer, the billing document view (VF03) showed all 15 line items, the delivery line items showed all 15 lines, but the sales order only showed the first 8 line items. The other last 7 items were not to be seen anywhere on the sales order.
Is there a maximum view limit on sales orders? Anyone else has had a similar case?
Thanks
Sandip

Hi Balaji,
I tried to access SE51 but I have no authorization, and even though I maintain user accounts at my company I could not find more details in regards to this Tcode.
I even tried to find some role associated with it but was unsuccessful.
Hi Chandrasekhar,
For the information in VOV8, the Display Range had 'UALL' in the field.
And wierdly, when I clicked on the Item Overview, all items (15 different types) are shown, but when going back into the Sales Order View for the same order, only the first 8 are shown.
The main problem here is that when doing a ZRE sales order, as we cannot do 'post goods receipt' for the 9th+n item.
I appreciate the help.

Sales information systems

please help me in SIS how i can configure the system so that based on the order type say OR standard order type i can get all the related information in SIS based on the order type

Hi Vikas,
Please find below the complete document on SIS:
Step-by-Step Guide to Activating a Self-Defined SIS Structure
IMG menu path for SIS: IMG>Logistics General>Logistics Information System (LIS)
Figure 1: IMG menu path for SIS configuration steps
Task 1: Create Self-Defined Information Structure
Use transaction code MC21 (menu path Logistics Data Warehouse>Data Basis>Information Structures>Maintain self-defined information structures> Create) to create a Self-Defined Information Structure. Give a customer-range number 990 (any available number between 501 and 999). To make it easier, use copy from to copy structure from S001.
Figure 2: Create a Self-Defined Info Structure
Figure 3: Structure S990 is created as a copy of S001
Structure S990 is created as a copy of S001. Accordingly, you will see defaulted characteristics and key figures. Review various settings (unit, sum, etc.).
Add two more characteristics: Sales Order Number and Item Number.
Click on Choose Characteristics Icon and then click on Selection List icon to choose fields from field catalogs.
Choose field catalog SD: Bus transaction (order) by double-clicking it. Double-click on Sales Document and Sales document item from field catalog fields (you may need to scroll-down).
Figure 4: Choose fields Sales Document and Sales Document Item from Field Catalog
You can view technical names by toggling the Switch Display icon.
Figure 5: Switch display to view technical names
Make sure that you have selected correct characteristics as: MCVBAK-VBELN and MCVBAP-POSNR.
Click on Copy + Close icon and then click on Copy icon to accept the changes.
Review information
Double-click on characteristics and key figures to review technical information. This step is not mandatory, just for information.
Figure 6: Review technical field information for characteristics: Customer (KUNNR), Sales Order (VBELN), Item (POSNR) and Key figures: Incoming Order (AENETWR), Open Order (OAUWE)
System displays the generation log.
Figure 7: Generation log for Structure S990. Table S990E is Structural Information for Table S990
Task 2: Maintain Update Groups
SIS IMG>Logistics Data Warehouse>Updating>Updating Definition>General Definition Using Update Groups>Maintain Update Groups
Figure 8: Update Groups for Sales and Distribution
No new entries need to be created. You can use the existing system-delivered update groups. Use Update Group (UpdGrp) 1 for the standard order process of: SIS: Sales Document, Delivery, Billing Document and use UpdGrp 2 for the SIS: Returns, Returns Delivery, Credit Memo.
Task 3: Maintain Update Rules
SIS IMG>Logistics Data Warehouse>Updating>Updating Definition>Specific definition using Update Rules>Maintain Update Rules>Display
Info Structure S001 and Update Group 1.
Before we create update rules for S990, let's review how update rules are defined for S001. Review rules for Characteristics and key figures.
Figure 9: Update Rules for combination of Structure S001 and Update Group 1
Double-click to review specific details of the update rule for Key Figure Incoming Orders. Note that the event is VA Sales Order creation.
Figure 10: Update rules for Key Figure Incoming Orders
Figure 11: Characteristics for Incoming Orders
Similarly review details of Key Figure Sales. Note that the Invoiced Amount (Sales Amount) is updated by event VD Billing Document.
Figure 11: Update rules for Key Figure Sales
Figure 12: Characteristics for Sales
Similar to Update Rules of S001, we need to create Update Rules for our Self-Defined Structure S990.
SIS IMG>Logistics Data Warehouse>Updating>Updating Definition>Specific definition using Update Rules>Maintain Update Rules>Create (transaction code MC24). To make it easier, use copy from to copy update rules from S001.
Figure 13: Create Update Rules for Structure S990
Please make sure the Source information is properly updated for all the characteristics. Since you copied the rules, the sales order and item rules are defaulted too. Make sure appropriate changes are made for events VC (delivery) and VD (Invoice).
Figure 14: Source Characteristics for Sales Document and Item
Since we copied the Update Rules, the source field and table information is also copied. We need to change appropriately to make sure correct source information is populated. Click on Rules for charact and verify source information for every key figure, by clicking on previous key figure and next key figure.
Figure 15: For Event VD Billing Document, Sales Document and Item are present in MCVBRP table
Figure 16: For Event VC Shipping, Sales Document and Item are present in MCLIPS table
Change Source information for following to MCVBRP-AUBEL and MCVBRP-AUPOS:
o Sales
o Gross Invoiced Sales
o Net Invoiced Sls 1
o Net Invoiced Sls 2
o Inv freight Chrgs
o Bill Docmnt PS5
o Bill Docmnt PS6
o Invoiced Qty
o Invoiced sls cost
Change Source information for following to MCLIPS-VGBEL and MCLIPS-VGPOS:
o Open Orders
o Open Order Qty
- Save and Generate by clicking on the Generate icon.
Similarly, copy update rules for Update Group 2. Transaction Code MC24.
Repeat these rules for the combination of information structure S990 and update group 2. (Copy from info structure S001 and Update group 2).
Figure 17: Maintain Update Rules for Structure S990 and Update Group 2
Again, click on Rules for charact and verify source information for every key figure, by clicking on previous key figure and next key figure.
Change Source information for following to MCVBRP-AUBEL and MCVBRP-AUPOS:
o Credit Memos
o Gross Credit Memos
o Net Credit Memos 1
o Net Credit Memos 2
o Credit memos freight
o Credit memos subtotal 5
o Credit memos subtotal 6
o Credit memos qty
o Credit memos cost
Task 4: Maintain Statistics Groups
Maintain Statistics Groups
Maintain Statistics Groups for Customers, Materials, SD Document Types etc. Most of the pre-defined settings are enough. Make sure that settings are updated for customized objects too, e.g., SD document types for your organizations.
Also, make sure that the customer (sales view) and material Master records are updated with appropriate Statistics Groups.
Figure 18: Maintain and assign statistics groups. IMG path: Updating> Updating Control> Settings: Sales> Statistics Groups
- Maintain Statistics Groups for Customers (OVRA)
Figure 19: Statistics Groups for Customers
- Maintain Statistics Groups for Material (OVRF)
Figure 20: Statistics Groups for Materials
- Maintain Statistics Groups for Sales Document
Figure 21: Statistics Groups for Sales Documents
- Assign Statistics Groups for relevant Sales Document Type
Figure 22: Assign Statistics Groups to relevant Sales Documents
- Assign Statistics Groups for each Sales Document Item Type
Figure 23: Assign Statistics Groups to relevant Item Categories
-Assign Statistics Groups to each Delivery Type
Figure 24: Assign Statistics Groups to relevant Delivery Types
-Assign Statistics Groups to each Delivery Item Type
Figure 25: Assign Statistics Groups to relevant Delivery Item Categories
- Determine Billing Document Types Relevant to Statistics
Figure 26: Assign Statistics Groups to relevant Billing Types
Note: As mentioned earlier, most of the settings are already set in standard system. Make sure that customized objects specific to your company are also updated appropriately.
- Update Customer Master for Statistics Relevancy
Transaction Code XD02 (Sales view, field Cust stats.Grp)
Figure 27: Assign Statistics Groups to Customer Master Records (Sales view)
- Update Material for Statistics Relevancy
Transaction Code MM02 (Sales 2 view, field Matl statistics grp)
Figure 28: Assign Statistics Groups to Material Master Records (Sales view)
Task 5: Assign Update Groups to Header and Item Levels
Assign Update Groups on Header and Item levels
For combinations of Sales Area (Sales Org, Distribution Channel, Division), assign Update groups (transaction codes OVRO and OVRP).
SIS IMG>Logistics Data Warehouse>Updating>Updating Control>Settings: Sales>Update Group
- Update Groups at Item Level
Figure 29: Update Groups at Item Level
Figure 30: Update Groups at Item Level - details
- Update Groups at Header Level
Figure 31: Update Groups at Header Level
Figure 32: Update Groups at Header Level - details.
Task 6: Activate SIS Update
Lastly, Activate SIS Update for the Structure (transaction code OMO1)
SIS IMG path: Logistics Data Warehouse>Updating>Updating Control>Activate Update>Choose Activity as Sales and Distribution.
Let's update our SIS structure S990 with period as Month and update option of Asynchronous Updating (2).
Figure 33: Activate SIS Update for S990
SIS tests with Sales Order Processing (Order>Delivery>Invoice)
Create a Sales Order, transaction code VA01
Figure 34: Create a standard Sales Order and Sales Order 6437 is saved
(Pricing details)
Figure 35: Pricing Details for the Sales Order
Execute transaction MC30 to find out which information structures are updated. Please note that this step is not mandatory.
Transaction code MC30 is worth mentioning here. This transaction code, provided user parameter MCL is set to X in users master record, provides analysis of which structures are updated for the activity. It generates a log of updates to Information Structures and detailed analysis. Since, it can take resources, it is advisable not to set user parameter MCL in productive system.
Figure 36: Transaction MC30 lists that Structure S990 is updated
Double-click on S990 line to view more details.
Figure 37: Transaction MC30 details for Structure S990
Execute Standard Analysis Report.
SAP>Logistics>Sales & Distribution>Sales Information System>Standard Analyses>Self defined analysis (transaction code MCSI). (Choose Structure S990). Enter appropriate values and execute.
Figure 38: Standard Analysis report for Structure S990
Figure 39: Standard Analysis report for Structure S990 for given criteria
Create a Delivery/PGI and review its impact on Standard Analysis Report.
Delivery 80007493 Saved, execute MC30 to review the update log.
Figure 40: At the time of Delivery/PGI, Structure S990 is updated
Figure 41: At the time of delivery, since Order is no more open, Open Order value is reduced
Please note in the Standard Analysis report that the Open Order value is reduced accordingly.
Figure 42: Standard Analysis report reflects correct Open Order value
Create an Invoice and review SIS report.
Invoice 90021696 saved. Review Update log with MC30.
Figure 43: Invoiced/Sales amount is updated at the time of invoice
Note that in the Standard Analysis report, Sales value has increased.
Figure 44: Standard Analysis report reflects correct Sales Amount
Summary changes in Information structure depending upon Sales activity
Sales Order: Note Open Order has EUR 49.60 value.
Delivery: Note Open Order value is reduced.
Invoice: Note Sales column reflects correct invoiced amount.
Figure 45: Summary Information Structures reflects correct values depending upon the status of transaction: whether order created, shipped or invoiced
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Unable to update Company Sales Information of the Account using Web service

Hi,
I am trying to update the Company Sales Information(Party Number, Customer number etc) of a existing Account through web Service 2.0 in dot net, but the values for
Company Sales Information remains unchanged. Also , when I am trying to insert a new Account through a web service, these fields remains blank.
I am not getting why this is happening.
Please help me if anyone knows about it.

Were you able to update other account information beside sales information? I'm doing the same - update sales information on the account - without any issues. Make sure to set external system id so that system can find the account that needs to be updated. Otherwise, I was getting "can't find the reference information" error. In my case I'm providing,
AccountData.setExternalSystemId("xxxxx");

Creation of Sales org views for customers related to vendor

Hello All,
Can any body tell me is there any functional module which can be used to created the sales org views for customers related to vendors.
Regards
Srinivas

Hi Ravi,
the number of sales area possible would be 6 sales area,
yes you can of course use the common master data functionality
After creating the organizational structure and relevant master records you want to use as the masters, that is, in the distribution channels and divisions you are going to use as a reference, you can group distribution channels and divisions separately for master data (which combines customer master and material master records), group condition records, or both master data and condition records.
Letu2019s say you have a product range that is not different for the four different distribution channels you have (the channels could be telesales, retail, industry, and wholesale.) Neither is there a difference in the customersu2019 details when they purchase through one or the other. Thus, you will not want to create a multiple of four views of customer master and material master records. Merely create the customer master records and material master records in one of the distribution channels, such as retail. Then assign the other distribution channels you created in the organizational structure setup to this one.
Donu2019t forget this means you can only create or change master data in the distribution channel that is being referenced. In the scenario above, this means you can only change data for the retail distribution channel. Even if you should access a customer or material master in change mode, press F4 (possible entries), and select telesales, industry, or wholesale, you will receive a message u201CSales area is not defined . . . u201D
The same is true for the sharing of conditions. If conditions are shared, you need only create a condition in the distribution channel or division you are using as the reference. Obviously, this only pertains to conditions that have the distribution channel and/or division in their key, such as a price based on sales area
Revert if helpful
Mohit Singh

Mm02 - Sales text view update?

Hi Friends,
I am working on the material master change (i.e MM02 transaction) and I need to upload Material master u2013sales text view and purchase order text view and all other additional data views.
I have updated one material in recording mode (i.e through SHDB transaction).
I am unable to find the sales text field name. But I find BDC_SUBSCR in my recording.
Pls find the below recording log.
SAPLMGMM     4040     X
BDC_OKCODE               =BU
            BDC_SUBSCR               SAPLMGMM                                 2010TABFRA1
            BDC_SUBSCR               SAPLMGD1                                1004SUB1
            MAKT-MAKTX               test material desc XXX
            BDC_SUBSCR               SAPLMGD1                                2121SUB2
Pls let me know how to update sales text view and po text view in MM02 transaction.
Thanks in advance.
Regards
raghu

You have to use FM SAVE_TEXT to upload sales text and purchase order test.
You can't record a BDC for custom controls like text editor.
MOVE V_MATNR TO tname-tdname.
MOVE 'MARA' TO TNAME-TDOBJECT.
MOVE 'SL1 TO TNAME-TDID.
MOVE SY-LANGU TO TNAME-TDSPRAS.
APPEND TNAME
TXTLINES-TDFORMAT = '*'.
TXTLINES-TDLINE = 'This is your purchase order text'.
APPEND TXTLINES.
CLEAR TXTLINES.
CALL FUNCTION 'SAVE_TEXT'
EXPORTING
CLIENT = SY-MANDT
HEADER = TNAME
INSERT = 'X'
SAVEMODE_DIRECT = 'X'
*OWNER_SPECIFIED = ' '
*LOCAL_CAT = ' '
IMPORTING
*FUNCTION =
NEWHEADER = TNAME
TABLES
LINES = TXTLINES
EXCEPTIONS
ID = 1
LANGUAGE = 2
NAME = 3
OBJECT = 4
OTHERS = 5
IF SY-SUBRC 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

Restricting the user options in the sales information system

Hi,
We use user information system for sales managers. We use T-code MCSI and the we choose customized information system S904.
Our goal is to restrict the options of each sales manager because we want that the sales manager only have access to his own information.
We try with the Parameter_ID VKB (sales office) but in this case the field is previosly filled but the sales manager can change it.
We use Authorization Data also but the sales manage still also can access to the sales of the others sales manegers.
How can i solve it?
Best Regards
João Fernandes

hi.
Please find the answer below :
"In addition to the type of update, you can also define the period unit to be used in the updating
process.
The period unit specifies the intervals in which the statistical data is to be cumulated. You can
choose from the following periods:
Day
Week
Month
Posting period (you may also need to specify a fiscal year variant)
You can determine the period unit of the update for every standard information structure.
In the SAP standard system, the default period unit for updating all the information structures in
the Sales Information System is month."
Hope this will help you .
Regards,
Krishna O

Using general hierarchy of sales information system

Hi,
The sales manager uses oftenly the general hierarchy in order to sort the information that could extract from sales information system.
So, firstly he uses the tranasction MCK1 to create a hierarchy and after that he executes the transaction MCSI in order to extract sales information.
So my question is, how can use the hierarchy in a abap program? I want to offer the hierarchy as selection parameter.
     Thank for your cooperation
                 Best Regards
                       João Fernandes

Hi,
Thank you for your answer but my question has not been answered.
The hierarchies i am talking are in table MCSHIERK. When i use program RGSEX000 i can not use the hierarchies of table MCSHIERK.
Can you give me somo more information now?
                Best Regards
                      João Fernandes

Events Sales Information System - Key figures

What key figure is updated in Net incoming orders 1 and Net incoming orders 2 as defined under update group 000001. I can understand Net incoming order and Gross incoming order.........

Hi Sanjay,
In order to separate both of the key figure groups the updating process is controlled via various update groups. Update group 000001 is assigned to the key figure group for incoming order information and update group 000002 to the group of returns key figures.
Assigning the business transactions to a certain update of statistics data takes place in two steps.
In the first step, you compile certain characteristics of the business transactions such as customer, material, document type into statistics groups. In the second step, you assign the statistics groups to the various update groups.
In the special case incoming order/returns, all of the returns order types are assigned to statistics group 02 and all other order types to statistics group 01. These different statistics groups are assigned to different update groups and thus key figure groups.
You can assign an update group to certain business transactions using the Customizing function in Sales
The two types of key figure groups used in the Sales Information System are invoice values and credit memo values. These key figure groups are differentiated by the different update groups (000001/000002).
Assigning certain types of invoices to the update group 000001 and types of credit memos to update group 000002 is done automatically by the types of orders belonging to them.
Just go through the following very useful link below:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/c1/3756d5449a11d188fe0000e8322f96/frameset.htm
Hope it helps...

Sales Information System Procedure with example

Hi Experts,
i need some documents or notes on the Logistics Information System (Specially Sales Information System) procedure wth some example.
my mail id : <REMOVED>
Thanks in advance
raj
Message was edited by:
Yathish K

Hi,
Please <b>read the rules of engagement</b> before posting.
<b>- Do not ask to send you an email.</b>
The question you ask and the solution to it is often also interesting for other users of the community. If you ask somebody to send you the answer per email, you deprive others of also learning to know the answer. Therefore any requests for sending material or answers to an email address will be modified by the forum moderators.

Sales Information System Performance Transaction MCSI

Hi,
We create a few years ago some Sales Information System using structures and tables Snnn. This structures/tables are accessible from transaction MCSI .
Right now the performance of the access to this information is very bad. We need a lot of time to use this SD Information System.
What can we do about this? Is it some notes about that, or some best practices?
Best Regards
João Fernandes

Please help any while creating sales order facing problem company code and language DE is not maintained, where i mis to maintain?

Maintain sales text View through BAPI_MATERIAL_SAVEDATA

Hi,
in BAPI_MATERIAL_SAVEDATA, can we maintain the Sales Text view in mm02 through this BAPI.
Regards,
Masoom Ali

Hi,
Fill the data in BAPI structure "MATERIALLONGTEXT".
Pass following parameters in the structure
APPLOBJECT : MVKE
TEXT_NAME : {Material+SalesOrg+Dist Channel}
TEXT_ID : 0001
LANGU : sy-langu
FORMAT_COL : *
TEXT_LINE : "Sales text which is to be updated"
Regards
Vinod
Edited by: Vinod Kumar on Jul 23, 2010 4:49 PM

Add new tab under 'Sales Area view/Data' of Customer Master TransactionXD01

Hi,
I want to add a new tab under 'Sales Area view/Data' of Customer Master Transaction XD01.
Is there any screen exit for XD01/XD02/XD03?
Or will I have to go and change SAP screens?
Thanks in advance.
Srinivas P
9663397476

Hi,
I want to add a new tab under 'Sales Area view/Data' of Customer Master Transaction XD01.
Is there any screen exit for XD01/XD02/XD03?
Or will I have to go and change SAP screens?
Thanks in advance.
Srinivas P
9663397476

Dump:Sales Text View in Material master for FERT items

Dear Gurus,
I am Creating Material MAster record for Fert Item,
I am trying to maintain the Sales View of it but system is
giving me dump ,
I am getting the following message
"No text maintained; a blank text has been created in English
automatically
Message no. MM630
Diagnosis
For your convenience, a blank text has been created in the
language English automatically.
Procedure
You can maintain this text. If you exit text maintenance
without maintaining it, it will be deleted automatically.
Name of runtime error
"LOAD_PROGRAM_NOT_FOUND"
Error analysis
On account of a branch in the program
(CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)
or a transaction call, another ABAP/4 program
is to be loaded, namely " ".
However, program " " does not exist in the library.
Possible reasons:
a) Wrong program name specified in an external PERFORM or
    SUBMIT or, when defining a new transaction, a new
    dialog module or a new function module.
b) Transport error
what can be the possible reason
Please guide me in this context
regards
shailesh

Dear Shailesh
If this is the problem , then please go through the solution
                                                                                No text maintained; a blank text has been created in English automatically
Message no. MM 630
Diagnosis
For your convenience, a blank text has been created in the language
     English automatically.
Procedure
You can maintain this text. If you exit text maintenance without
     maintaining it, it will be deleted automatically.
This is a standard behivour . No need to worry . it is not an error.It comes because you have to maintain something in sales text view if the sales view is maintained in OMS2 settings.And since it is a finished material then it will come.
It dosent allow you to go to the next view when you press enter .
you have to go to the next view using Mouse .
Just click on the next view you have to create it will allow.
then fill all the views and just save the material you will be able to save
Regards
Rahul Singh
Edited by: Rahul Singh on Nov 19, 2008 8:11 AM

Standard SD Reports under sales information syatem

Hi,
How to configure Standard SD Reports which fall under sales information system.Kindly tell me the
process of configuring these reports in detail in SPRO
Regards
Rahul

If it is LIS there are two important things:
1) Statistics update configuration should be done at Header level OVRO and item level OVRP for the sales area.
2) Customer statistics group and material statistics group should be filled in customer and material master respectively.
Regards,
GSL.

Sales information view in PS

Similar Messages

Maybe you are looking for