Sales order table control

Hi Experts,
I want to upload sales order information (va01 transaction) from flat file to sap.
but in va01 tcode table control is there
so could you plz guide me whts the procedure to upload sales information.
points sure
Thanks in advance,
Divya sree

Hi,
When you have enter multiple line in BDC for a table control use call transaction code using i_bdcdata options from opt message into i_messages.
Check the below example.
data: lws_cnt type char2,
lws_field type char15.
LOOP AT i_invoicing_plan INTO wa_invoicing_plan.
lws_cnt = sy-tabix.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = lws_cnt
IMPORTING
output = lws_cnt .
CONCATENATE 'FPLT-AFDAT(' lws_cnt ')' INTO lws_field.
CONCATENATE wa_invoicing_plan-date+6(2)
wa_invoicing_plan-date+4(2)
wa_invoicing_plan-date+0(4) INTO lws_date
SEPARATED BY '.'.
PERFORM bdc_field USING lws_field lws_date.
CONCATENATE 'FPLT-FPROZ(' lws_cnt ')' INTO lws_field.
lws_perct = wa_invoicing_plan-percentage.
CONDENSE lws_perct.
PERFORM bdc_field USING lws_field lws_perct.
ENDLOOP.
While calling the transaction give like this:
DATA: opt TYPE ctu_params.
opt-dismode = 'N'.
opt-updmode = 'A'.
opt-defsize = 'X'.
CALL TRANSACTION tcode
USING i_bdcdata OPTIONS FROM opt MESSAGES INTO i_messages.
LOOP AT i_messages.
ENDLOOP.
Regards
Pavan

Similar Messages

Sale order table to bi

I want to bring the sale order table to BI. What are the activities required to be done in r/3 as well as in bi.

Hi.........
It depends which fields u want to extract..............If there are any Standard Datasource then u can use it...............otherwise u can go for Generic datasource.............since SD belongs to LO Extraction...........U hav to follow the below Steps........
The following section describes the steps that are necessary to configure a data
flow for logistics data extraction.
1. Transfer the logistics DataSource for transaction data from Business Content
With the transfer of the DataSource, the associated extraction structure is
also delivered, but the extraction structure is based on LIS communication
structures. Furthermore, based on the extraction structure for the DataSource,
a restructuring table that is used for the initialization and full update to BI
is generated.
Naming convention:
DataSource 2LIS_<Application>_<Event><Suffix>; where <Event> is
optional
Examples:
2LIS_11_VAITM: 11 = SD Sales VA = sales order, delivery schedule ITM
(u2192 ITEM) = document position
Extraction structure MC<Application><Event/group of
events>0<Suffix>; where MC is derived from the associated communication
structures and <Suffix> is optional
Examples:
MC11VA0ITM: Extraction structure for the DataSource 2LIS_11_VAITM
MC02M_0HDR: Extraction structure for the DataSource 2LIS_02_HDR,
where M_ indicates the group for the events MA (order), MD (delivery
schedule), ME (contact) and MF (request).
Restructuring table (= setup table) <Extraction structure>SETUP
Example:
Extraction structure: MC11VA0IT u21D2 Restructuring table:
MC11VA0ITSETUP
2. Maintain extraction structure (transaction LBWE)
This means that fields can be added to the extraction structure that is
delivered with the DataSource without modifying anything. On the one
hand, fields from the LIS communication structures that are assigned to the
extraction structure can be used, that means standard fields that SAP has
not selected, and on the other hand, customer fields that were attached to
the LIS communication structures with the append technique can be used.
After the extraction structure is created, it is generated automatically and the
associated restructuring table is adapted.
3. Maintain/generate DataSource
In the DataSource maintenance, you can assign the properties Selection,
Hide, Inversion (= Cancellation) and Field Only Known in Customer Exit to
the fields of the extraction structure. After enhancing the extraction structure,
the DataSource always has to be generated again!
4. Replicate and activate DataSource in SAP BI (=metadata upload)
5. Maintain Data Target (Data Store Object, InfoCube)
6. Maintain Transformations between DataSource and Data Target
7. Create a Data Transfer Process
the Data Transfer Process will be used later to update the data from the PSA
table into the Data Target.
8. Set extraction structure for updating to active (transaction LBWE)
In this way, data can be written to the restructuring table or the delta queue
from then on using the extraction structure (see following steps).
9. Filling the restructuring table/restructure (OLI*BW)
During this process, no documents should be created or changed in the
system! In some applications, it is possible to fill the restructuring table
beforehand in simulation mode. These results are listed in a log (transaction
LBWF). Before filling the restructuring table, you must ensure that the
content of the tables is deleted (transaction LBWG), preventing the table
from being filled multiple times. Once the restructuring tables are filled,
document editing can resume as long as Unserialized V3 Update or Queued
Delta is selected in the next step. Be absolutely sure that no V3 collection
run is started until the next successful posting of an InfoPackage for delta
initialization (see step 11).
10. Select update method
Unserialized V3 update
Queued delta
Direct delta
11. Create an InfoPackage for the DataSource and schedule the Delta
Initialization in the Scheduler
This updates the BI-relevant data from the restructuring table to the
PSA table. Since the restructuring table is no longer needed after delta
initialization, the content can be deleted (transaction LBWG).
Use the Data Transfer Process created in step 7 to update the data from
the PSA table into the Data Targets. After successful delta initialization,
document editing can resume, as long as the direct delta update method
was selected in step 13. This means that BI-relevant delta data is written
directly to the delta queue.
Note:
If the DataSource supports early-delta initialization, the delta data can
be written to the delta queue during delta initialization. This feature is
controlled with an indicator in the Scheduler.
12. Start V3 collection run (transaction LBWE)
This step is only necessary when the update method unserialized V3 Update
or Queued Delta was selected in step 10. By starting a corresponding job for
an application, the BI-relevant delta data is read from the update tables or
extraction queue and written to the delta queue.
13. Create an InfoPackage for the DataSource in BI and schedule the Delta
Update in the Scheduler
The BI-relevant delta data from the delta queue for the DataSource is updated
to the PSA table. Use the Data Transfer Process created in step 7 to update
the data from the PSA table into the Data Targets.
And if u want to create a Generic datasource............use tcode RSO2.................if u r Extracting data from a single table...........then create the datasource based on the condition table.................if u r extracting from two or three tables go for View...............and if u r extracting data from many tables...........its better to go for function module...........If u don't know how to create generic datasource.........U can search in Forum.............u will get good documents..........
Hope this helps.........
Regards,
Debjani...............

Purchase order and sales order table name

hi al,
i want to know purchase order and sales order table name in abap.
thanks
varun
Moderator message: please do some own research, this should not take too long.
Edited by: Thomas Zloch on Jan 27, 2012

Hi Sunrag......
If your PO is linked with SO. Then you can fetch customer name easily by FMS in PO.
From there you ca gte the Customer Name into your PLD and it wont hang also.....
Regards,
Rahul

Invoice Receipt document (TABLE RBKP) based on Sales Order (table VBAK).

Hi Folks,
I have to find Invoice Receipt document (Table RBKP) based on Sales Order (table VBAK).
Please tell me how the two documents are linked.
Thanks,
Punit

I don't know table RBKP, but I would start by seeing if I could find the value of RBKP-BELNR or XBLNR as the next document in table VBFA. If found, then you know how to read VBFA forward from sales order (VBAK) to VBFA with correct next document type, then to RBKP with the document number....
Don't know if this will work, but this is the first approach I would take.

ALE / IDOC / sales order customer control record change

I'm trying to look for a "standard" answer. Here's my problem:
Record comes into SAP with a non-sap customer number that needs translated to SAP customer number.
Options I'm looking into:
1. Use the user exit and pull the customer characteristic from the customer master. Based on the characteristics then convert the control record.
2. Use the user exit at the sales order create. Based on the characteristics then convert the sales order and do not convert the control record.
3. Use standard EDPAR and convert the control record.
The problems:
If I use code to change the sold to custmer number at the control record level, I'd like to do the same thing at the detail level. The standard SAP code uses EDPAR. There are many different user exits based on the IDOC type in the system. I really don't want to change the code for each one.
EDPAR is maintained by IS. However, the customer master is in the business hands and is easily used. The customer master would be the perfered way to do things.
Any suggestions? Has anyone else had a problem with the customer number in the control record? We used to do it prior to moving the record into the SAP system. We would like to move away from that.
Thank you!
Michelle

OK so we have a strange setup. Yes, sold-to and ship-to is in the sales order.
The customer number in the control record is really our SAP sold-to number. It also is the partner number.   It is required for WE20. However when the IDOC comes into our system our customer doesn't always send the partner number. They can send their number for our company, the DUNS number or others. We have to take that number and convert it to our partner number.
While conversion from X12 to IDoc, based on the ISA ID or Sold-to party number you should map the correct SAP partner number onto the control record.
Coming to non-SAP sold-to party number in E1EDKA1 segment, the same non-sap sold-to number can be mapped to this segment but you should maintain EDPAR Entries. (VOE4).   Yes, I found that EDPAR seems to be the way SAP is expecting the conversions. However, we want our customer service to maintain the conversion.   That means that it has to be in a good format. So I could write a Z transaction over the EDPAR table for easier maintenance, or use the customer master screens. The customer master seems to be a logical place for custmer service to enter in the conversions. However, EDPAR is what SAP is expecting. So I decided to have them update the customer master via characteristics, and then use a BADI to send the information to EDPAR. Use "standard" functionality to change the control record. I believe it is a user exit.
Any questions?? I always have questions.   I think the above solution will work.   We haven't prototyped it yet.   That will happen soon.    My question was very generic and probably hard to follow.
Hopefully this clears up what I think we are going to do. Any other solutions would be appreciated.   The control record may or may not be correct when it is recieved. So we need to convert. Another requirement is that customer service has to set up the conversion values. VOE4 is not a good transaction for non-technical people to use.   So we need a better way.
Again we have voted to try the above solution. But I welcome any other suggestions.
Thannk you,
Michelle

Sales order credit control area

Hi,
How can i identify the credit control area the sales order belongs to?
Is there any way to identify in the SO itself?
(not checking the sales org and checking the cc ar)

Credit Control
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
   Check which credit control area is assigned to the company code.
   Company code:
   Credit control area:
2. Transaction OVFL
   Check which credit control area is assigned to the sales area.
   Sales area:
   Credit control area:
3. Transaction XD02 or VD02
   Check which credit control area is assigned to the payer.
   Payer:
   Credit control area:
4. Transaction SE37
   Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
   For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
   OB45, or the credit control area must be entered under the relevant company code in table
   T001CM of the credit control areas allowed.
   Company code:
   Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
   Which settings do exist for the sales document type used?
   Sales document:
   Check credit:
   Credit group:
8. Transaction OVAD
   Which settings do exist for the delivery type used?
   Delivery type:
   Credit group for delivery:
   Credit group for goods issue:
9. Transaction OB01
   Credit management/Change risk category
   Definition of the risk category for each credit control area. This risk category can be
   assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
    Here, the individual credit checks for key fields
    o credit control area
    o risk category
    o credit group are set. Take these key fields from the above settings and go to the detail
      screen. In particular, check whether fields "Reaction" and "Status/block" are set
      correctly. To carry out follow-up actions in case of a credit block, the credit check
      status must be set (field "Status/block").
11. Transaction FD32
    Credit master data for the payer of the relevant document.
    Credit account:
    Credit limit:
    Risk category:
    Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit
    check (static or dynamic credit limit check).
13. Transaction OVA7
    Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to
    field "Active receivable" in Transaction VOV7.
    Item type:
    Active receivable:
14. Transaction V/08, Pricing
    In the pricing procedure used for pricing, subtotal "A" must be entered in a line for
    determining the credit value (mark the pricing procedure and doubleclick on "Control").
    Usually, the net value plus taxes is used. This way the system is determined to use this
    subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for
    update and credit check.
    You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
    Pricing procedure:
    Line with subtotal = 'A':
15. Transaction OB45
    Which update group (field "Update") do you use in the relevant credit control area? The
    default setting is "12". If you use another update group, check whether this is fine with
    you. If you open an OSS message, please tell us the alternative update group.
    Credit control area:
    Update:
16. Transaction OMO1
    Which kind of update did you choose for structure S066?
     In any case, "Synchronous update (1)" has to be chosen as the kind of update.
     All other settings will lead to errors.
Credit Management
All business have their own credit management needs, SAP allows you to specify your own automatic credit checks based on a variety of criteria. You can also specify at which critical points in the sales and distribution cycle the system carries out these checks.
u2022 SM30 - Table/View
u2022 V_TVTW - Define Distribution Channel
u2022 V_TVTA_KKB - Assign sales area to credit control area
u2022 V_T014 - FI - Define Credit Control Area
u2022 T001CM - FI - Assign Permitted Credit Control Area to company code
OVXG - Set up Sales Areas
e.g. Sales Organization
Distribution Channel
Division
Distribution Channel
Division
FD32 - Customer Credit Management
OVAK - Define credit limit check by sales document type
u2022 Check Credit
o A - Credit limit check and warning message
o B - Credit limit check and error message (no sales order can be created)
o C - Credit limit check and delivery block (block delivery if hit credit limit)
 Options B and C -> used for checking open order values (when you create/change the sales order)
o D - Automatic credit control with open order values
 More control in transaction OVA8 - Automatic credit control
 You check for open orders and deliveries, or just open deliveries.
 or open order values with other options
u2022 Credit group
o Allows you to combine different sales document types for the credit limit check
VKM1 - Blocked SD Documents - Finance have to released the delivery block
OVAD - Define credit limit check by delivery order
u2022 whether the automatic credit check occurs at the time of delivery creation and/or goods issue
OVA7 - Define credit limit check by item category
u2022 Set whether to include/exclude item category for credit limit check
OVA6 - Define credit group. You can groups together different business transactions which should be dealt with in the same manner with regard to the credit check.
You enter the credit groups when you configure the sales document types for credit management and define the (D - automatic credit check).
u2022 SAP default credit groups
o 01 - credit group for sales order
o 02 - credit group for delivery
o 03 - credit group for goods issue
OVA8 - Automatic credit control - Double click on the line items you can have the followings credit limit check:-
u2022 Static
Depends on the customer total value of open orders, deliveries, billing documents and open items.
u2022 Open items
No of days open
Overdue open items checks is based on the ratio of open items that are overdue by a certain number of days.Max open items %
The customer balance must not exceed a certain percentage.
u2022 Oldest open items
If you donu2019t want to deliver to the customer at all when even only 1 invoice is overdue.
Tick the Check for Oldest Open Item and Set the field Days oldest item = 1.Days oldest item
No of days allowed for overdue or payment terms.
Use of the credit check Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
that was previously blocked, it would be reblocked again by the system. The system only reblocks the sales document if the new order quantity is above a certain % amount.
u2022 Released documents are still unchecked
The preset % is whatever you want to set it as when configuring your automatic credit processing. You enter a deviation % and number of days,eg, you can set it so that an order can be changed by up to 10% within 30 days of original order entry date without it going back on credit block.
u2022 Next Review Date
If a customer has a credit limit of 1000 USD, and you would like to restrict this credit limit only to be available in current month (say March). If the document day is in April then the credit limit is zero.You can use the u201CNextReview dateu201D and u201CNumber of daysu201D fields and combined it with the u201CLast int.reviewu201D field in customer credit master u201CStatusu201D view (FD32).
VOKR - Display of work list for credit management (configure the display variant)
Releasing the Credit Block
These are the three transaction code you can used for releasing the SAP credit management block.
VKM3 - Sales Order
VKM5 - Delivery Order
VKM4 - Both Sales Order and Delivery Order
There are basically two types of customers:
1)Credit worthy
2)Normal customers
Coming to credit worthy customers these customers we can believe and we will give some credit ness for them.For such a type of customers we are going to set them some credit limit.Based on that we will give service to them till that limit.It the limit crosses we will get the messages while creating orders for them.
Their credit limit can be set in FD32 T.Code.
Automatic credit check will be maintained in OVA8
Follow these steps:
1. Go to IMG - enterprise structure - definition - financial accounting - define credit control area.
2. Assignment of company code to credit control area & sales area to credit control area.
3. Go to OVAK select ur sales document type and in the check credit column choose from A B or C. D is for automatic credit control for which you have to maintain the credit group and risk categories.
4. In FD32 you select your customer and click on STATUS icon and press enter. here u maintain the credit amount allowed. but this is done by the Finance people.
5. Now when you create the sales order and if the amount exceeds the credit limit then u will get the message as you maintained in the TC OVAK. Normally the system starts doing credit checks from the second sales.
order.
What are the different types of credit checks?
By Sunilmadho
Credit Check can be :
1) Simple Credit Check
2) Automatic Credit Control
Automatic Credit Control can be at various levels :
1) Order
2) Delivery
3) Goods Issue
Automatic Credit Check is of many types :
1) Static
2) Dynamic
3) MaximumDocument Value
4) Maximum Open Items in percentage
5) Oldest Open Item in number of days
6) Crtitical fields change
7) Highest dunning level, etc.
You can create more.
Credit Check happens only in SD module, never in FI. Because the stage of the check is in the sales cycle, which exists in SD. FI guys will check the credit master sheets of the customer, the MIS, the analysis etc, review the credit limits of customers. But the check will happen only in SD, while creating order, delivery or doing the goods issue.
All business have their own credit management needs, SAP allows you to specify your own automatic credit checks based on a variety of criteria. You can also specify at which critical points in the sales and distribution cycle the system carries out these checks.
SM30 - Table/View
u2022     V_TVTW - Define Distribution Channel
u2022     V_TVTA_KKB - Assign sales area to credit control area
u2022     V_T014 - FI - Define Credit Control Area
u2022     T001CM - FI - Assign Permitted Credit Control Area to company code
OVXG - Set up Sales Areas
e.g. Sales Organization
                  Distribution Channel
                              Division
                  Distribution Channel
                              Division
FD32 - Customer Credit Management
OVAK - Define credit limit check by sales document type
u2022     Check Credit
o     A - Credit limit check and warning message
o     B - Credit limit check and error message (no sales order can be created)
o     C - Credit limit check and delivery block (block delivery if hit credit limit)
     Options B and C -> used for checking open order values (when you create/change the sales order)
o     D - Automatic credit control with open order values
     More control in transaction OVA8 - Automatic credit control
     You check for open orders and deliveries, or just open deliveries.
     or open order values with other options
u2022     Credit group
o     Allows you to combine different sales document types for the credit limit check
VKM1 - Blocked SD Documents - Finance have to released the delivery block
OVAD - Define credit limit check by delivery order
u2022     whether the automatic credit check occurs at the time of delivery creation and/or goods issue
OVA7 - Define credit limit check by item category
u2022     Set whether to include/exclude item category for credit limit check
OVA6 - Define credit group. You can groups together different business transactions which should be dealt with in the same manner with regard to the credit check.
You enter the credit groups when you configure the sales document types for credit management and define the (D - automatic credit check).
u2022     SAP default credit groups
o     01 - credit group for sales order
o     02 - credit group for delivery
o     03 - credit group for goods issue
OVA8 - Automatic credit control - Double click on the line items
You can have the followings credit limit check :-
u2022     Static
Depends on the customer total value of open orders, deliveries, billing documents and open items.
u2022     Open items
No of days open
Overdue open items checks is based on the ratio of open items that are overdue by a certain number of days.
Max open items %
The customer balance must not exceed a certain percentage.
u2022     Oldest open items
If you don't want to deliver to the customer at all when even only 1 invoice is overdue.
Tick the Check for Oldest Open Item and Set the field Days oldest item = 1.
Days oldest item
No of days allowed for overdue or payment terms.
Use of the credit check Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
that was previously blocked, it would be reblocked again by the system. The system only reblocks the sales document if the new order quantity is above a certain % amount.
u2022     Released documents are still unchecked
The preset % is whatever you want to set it as when configuring your automatic credit processing. You enter a deviation % and number of days,eg, you can set it so that an order can be changed by up to 10% within 30 days of original order entry date without it going back on credit block.
u2022     Next Review Date
If a customer has a credit limit of 1000 USD, and you would like to restrict this credit limit only to be available in current month (say March). If the document day is in April then the credit limit is zero.
You can use the "NextReview date" and "Number of days" fields and combined it with the "Last int.review" field in customer credit master "Status" view (FD32).
VOKR - Display of work list for credit management (configure the display variant)
In credit mgmt how the Amount & limit can be can be configured at sales order,delivery & PGI Level.
Please give me the solution .
1)First create Credit control area
Path:IMG\ES\Definition\FA\Define Credit Control Area
2) Assign your credit control area to your company code
Path:IMG\ES\Assignment\FA\Assign Company code Credit Control Area
3) And enter the credit limit using above mentioned transaction code FD32.
4) And assign this credit control area in your customer master Sales Org Data (XD02)
5)if you have maintained the credit control area for your customer then goto T.Code FD32.
6)Enter your customer number and the credit control area.
7)Select the status tab.Press enter.
8)Maintain the credit limit in the field.Save.
9)Go to OVA8 T.Code and then click on open orde

Open Sales Order table with multiple schedule line....

YUSUF BHORI wrote:
Hi Experts,
In Sales Order there are multiple schedule line for single item.
Where and in which table i can find open qty for order ,material, item and schedule line items.
I Want open items for each schedule line. For One vbeln, posnr there multiple etenr.
Urgent,
Yusuf.

Hai,
Join VBAK & VBAP and store data in an internal table GT_VBAP to get Sales order numbers, items, materials.
Get Open Sales order items from VBUP into GT_VBUP where VBUP-GBSTA NE 'C'.
LOOP at GT_VBAP.
Read table GT_VBUP with key vbeln & posnr.
If sy-subrc <> 0.
delete GT_VBAP.
endif.
****Fill your Final Report Internal table with required field values **Append into that internal table
ENDLOOP.
Now Select WMENG BMENG from VBEP into GT_VBEP for all entries in GT_VBAP.
LOOP AT GT_VBEP.
*******Again Modify your Final Report internal table with these values
***VBEP-WMENG is Ordered Qty
***VBEP-BMENG is Confirmed Qty
************Open Qty = Ordered Qty = Confirmed Qty***
************Open Qty = VBEP-WMENG = VBEP-BMENG.***
ENDLOOP.
Edited by: Eswara Rao Aakula on Dec 24, 2007 9:56 AM
Edited by: Eswara Rao Aakula on Dec 24, 2007 9:57 AM

Purchase Order Table Control

Hi,
I am trying to change the columns in the table control of the purchase order screen (ME21N) but cant seem to able to do it,
To be more detailed I clicked on the "Configuration" button of the table control, clicked on "Administrator" and made the fields "plant/MEPO1211-WERKS" and "storage location/MEPO1211-RESLO" visible ( unchecked the fields ) but the table control does not change, I have activated the changes even created a new variant for the settings but no changes are seen, I have tried to make the other fields visible/invisible but no changes are seen.
Help is greatly appreciated.
Thanks

Please check out the following note.....
SAP Note No. 120901                          22.08.2005           Page 1
Number              120901
Version             5 from 08.06.2001
Status              Released for Customer
Set on              07.06.2001
Language            EN
Master language     DE
Short text          Hiding of columns by table control is not possible
Responsible         SAP AG
Component           MM-PUR
                    Purchasing
Long text
Symptom
Using the table control configuration, you are unable to hide the
columns on the overview screens of the purchasing documents (purchase
requisition, purchase order, request for quotation, outline agreement).
Additional key words
ME21, ME51, ME41, ME31, ME31K, ME31L, ME21N, ME22N, ME23N, OMF4
Cause and prerequisites
The hiding of fields was and still is controlled by Customizing.Here,
you can - with the help of the field selection key - make fields
invisible (for example, for a particular document type). This setting
overrides the individual table control setting.
Solution
It is currently not possible to hide columns selectively for each user.
Instead, SAP recommends that you shift the columns you do not require in
the table control to the far right and save this setting.
If this was helpful, please award points accordingly . Thanks.
Regards,
Rich Heilman

Pricing- Sales Order - tables

Hi ,
In our system, the base price(PR00) has 6 different access sequence. Trying to figure out which access sequence was applied to the sales order item.
Need to generate a report of sales order items with pricing codnitions along with access sequence details.
Able to get the pricing details from KONV but this does not have the access sequence details for each condition type. Could you please advise if there is function module / table from where I can get this ifnormation.
please advise.
Thank you.

I've never seen the pricing determination details stored anywhere....there is the ability to show the pricing determination, though, within the order... However, it may be in a table somewhere...of course, we can get to the results in the condition tables, but I don't recall that showing the determination and pricing tables used, etc. I can't check; my employer doesn't utilize Logistics.

Sales order tables

Hi Guru,
Can anybody tell me in which tables the data in sales order like delivering plant, total weight, unit of weight, volume, volume unit etc stored.
For example in my sales order the delivery plant for Sales Order no 100 is J100, in which table is this value J100 stored? I am unable to locate it in VBAK, VBKD or VBAP.
When i try to get it from technical info, i find that it is in structures
RV45A     DWERK
RV45A     BTGEW
RV45A     GEWEI
RV45A     VOLUM
RV45A     VOLEH
Can anybody tell me where the values for these fields are stored?
Thanks,
Venkat

I quickly checked
BTGEW is not the filed you can change
BRGEW you can change for each position and it is stored in VBEP-BRGEW (here I was wrong in last post. You can change what was taken from material master and this will be stored in VBAP table).
BTGEW is calculated value, because the F1 help says its total and its calculated.
I think this answers your question.
regards
Rafal
Edited by: Rafal Drezek on Jul 9, 2009 4:37 PM
Edited by: Rafal Drezek on Jul 9, 2009 4:38 PM

Disable Document Flow in Sales Order copy control

Hello,
We have a request where the customer doesn't want the docflow to appear when you copy a sales order to another sales order? I know that you can disable the flag for the item categories however, when you do this, there is still a link between a sales order when it's created by referencing another. Is there a way to create a sales order via "copy with reference" and to not have them linked in the docflow? Possibly one of the configuation settings in the copying control? We are on 6.0.
Thanks,
Chris

Hi,
I think It is not possible through configuration.
Pl try screen exit
or
change in standard program,which is not advisable.
Thanks,
Vrajesh
Edited by: Vrajesh G. Nayak on May 4, 2010 1:36 PM

Sales order Table Payment card

HI
In sales order -overview screen sales tab we have
Payment card & Exp.date field Pl let me know in which TABLE-FIELD these data will be stored

Hi
Please find the tables below
CCDATE---EXDATBI -
Date up to which the payment card is valid.
CCDATA---CCINS -
Specifies the card type of the payment card.
REgards
Damu

Joins between transactions and sales order tables?

Hi all,
SELECT ott.NAME,
             msi.organization_id
FROM apps.mtl_material_transactions mmt,
            apps.mtl_system_items_kfv msi,
            apps.oe_order_headers_all ooha,
            apps.oe_order_lines_all oola,
            apps.oe_transaction_types_tl ott
WHERE     mmt.transaction_type_id = 12
       AND mmt.inventory_item_id = msi.inventory_item_id
       AND mmt.organization_id = msi.organization_id
       AND ooha.header_id = oola.header_id
       AND oola.line_id = mmt.trx_source_line_id
       AND oola.inventory_item_id= msi.inventory_item_id
       AND ooha.order_type_id= ott.transaction_type_id
       AND mmt.inventory_item_id = 1234
       AND msi.organization_id = 20
And i don't have inventory item id with this transaction_type_id = 12

Transaction_type_id 12 is a "Receive from Intransit". I don't think those will join to sales orders. What are you trying to accomplish?

Pricing Type D to work for sales order to sales order copy controls

Hi,
Issue: Pricing type D does not work while creating a debit memo request in reference to the credit memo request.
Credit memo request and debit memo request have identical pricing procedures.
But in this case, the credit memo was created with reference to a billing document which had a different pricing procedure and the pricing procedure components of the billing document was copied entirely into the credit memo request with pricing type D in the copy control.
But when this credit memo request is referenced to create a debit memo request with the pricing type D in the copy control, the price is re-determined in the debit memo request. But the scenario requires, the pricing elements to be copied completely from the credit memo request.
Please advise for the corrections or on the changes to be made to the requirement.
Thanks and Regards,
Gopinath
Edited by: Gopinath Naik R on May 18, 2009 5:31 PM

This is due to the Coopy Routine in Billing to Sales Doc.
In the Copy control routine of the Item , you find the routine being used, Inside this Routine , you will find a statement like
MOVE-CORROSPONDING CVBRK to VBAP
This statement is actually transfering all feilds from billing document to the Order with the Billing Pricing Procedure.
Just add one line before this statement " LOCAL CVBRK-KALSM
or
CVBRK-KALSM = VBAK-KALSM
This will give you the new Determined Pricing Procedure.
this is a change in code of the Routine , may be you need to copy and create a new routine to add this line.

Simulation in Bapi/FM for sales order is locking tables

Hi
We want to use bapi BAPI_SALESORDER_CHANGE or FM SD_SALESDOCUMENT_CHANGE to simulate the effect on prices of a sales order. We must do this during the printing of the sales order. This bapi/FM is locking the sales order tables during the simulation mode. As we are printing from the sales order, the sales order is already locked so we get the error: V1 042 Sales document xxx is currently being processed. Does anyone have a solution to avoid this lock or an alternative to simulate the price from a sales order?
We need to use the simulation of the sales order to capture all manual changes in the sales order pricing.
Kind Regards

Hi,
FM BAPI_SALESORDER_SIMULATE gives the same pricing data as BAPI_SALESORDER_CHANGE. you do not need to change an existing document to get the pricing data. Just simulate the creation of a new order.. th prices should be the same as long as you send the same data.
Dev.

Sales order table control

Similar Messages

Maybe you are looking for