Change Delivery Class of ZTable

We currently have a ZTABLE that is defined as Delivery Class 'A'. In each system (DEV, QAS, PRD) we modify the table using a Table Maintenance View and SM30. We now have a requirement to enforce promotion of the Data in the table from DEV to QAS to PRD. In my experiments, Delivery Class 'C' will provide this functionality; however, I am not sure if it is possible (or advisable) to change the Delivery Class of a Table already promoted to Production.
Has anyone had any experience with changing the Delivery Class of an existing table?
I've checked online documentation for Delivery Classes; so far this has explained how to initially choose a Delivery Class, but there has been no information on changing a Delivery Class or statements stating not to change the Delivery Class of a table. In addition I have Googled "SAP Change Delivery Class", "SAP Table Class" and "SAP Delivery Class"; these searches have yielded no results that answer this question.
The other option I am looking at involves building a new table with an identical structure of the Delivery Class 'C', then changing each application to read the new table instead of the existing table.
Any help and/or opinions will be appreciated.
Thank you,
Steven Coolbaugh

>
Steven Coolbaugh wrote:
> We currently have a ZTABLE that is defined as Delivery Class 'A'. In each system (DEV, QAS, PRD) we modify the table using a Table Maintenance View and SM30. We now have a requirement to enforce promotion of the Data in the table from DEV to QAS to PRD.
Hello Steven,
Whether or not table entries can be transported does not depend upon the "delivery class".
In my experiments, Delivery Class 'C' will provide this functionality
AFAIK this won't help. If the delivery class of the table is 'C', then you have to use a customizing request to transport the entries. To make the entries transportable you have to activate the "standard recording routine" radio-button in the table maintenance generator.
Hope this helps.
BR,
Suhas

Similar Messages

Delivery Class Changed To A

Hi All,
I have changed The Delivery Class for one of My custom Table from C to A .
Table Maintnance Gen is also availabole for this ..
Please inform , if i need to regenerate the TMG if yes what reason should i use for the regeneration .
Praveen.

Hi
see the doc of the delivery class
Delivery class
The delivery class controls the transport of table data when installing or upgrading, in a client copy and when transporting between customer systems. The delivery class is also used in the extended table maintenance.
There are the following delivery classes:
A: Application table (master and transaction data).
C: Customer table, data is maintained by the customer only.
L: Table for storing temporary data.
G: Customer table, SAP may insert new data records, but may not overwrite or delete existing data records. The customer namespace must be defined in table TRESC. (Use Report RDDKOR54 here).
E: System table with its own namespaces for customer entries. The customer namespace must be defined in table TRESC. (Use Report RDDKOR54 here.)
S: System table, data changes have the same status as program changes.
W: System table (e.g. table of the development environment) whose data is transported with its own transport objects (e.g. R3TR PROG, R3TR TABL, etc.).
Behavior during client copy
Only the data of client-specific tables is copied.
Classes C, G, E, S: The data records of the table are copied to the target client.
Classes W, L: The data records of the table are not copied to the target client.
Class A: Data records are only copied to the target client if explicitly requested (parameter option). Normally it does not make sense to transport such data, but is supported to permit you to copy an entire client environment.
Behavior during installation, upgrade and language import
The behavior differs here for client-specific and cross-client tables.
Client-specific tables
Classes A and C: Data is only imported into client 000. Existing data records are overwritten.
Classes E, S and W: Data is imported into all clients. Existing data records are overwritten.
Class G: Existing data records are overwritten in client 000. In all other clients, new data records are inserted, but existing data records are not overwritten.
Class L: No data is imported.
Cross-client tables
Classes A, L and C: No data is imported.
Classes E, S, and W: Data is imported. Exisitng data records with the same key are overwritten.
Classe G: Data records that do not exist are inserted, but existing data records are not overwritten.
Behavior during transport between customer systems
Data records of tables of delivery class L are not imported into the target system. Data records of tables of delivery classes A, C, E, G, S and W are imported into the target system (this is done for the target client specified in the transport for client-specific tables).
Use of the delivery class in the extended table maintenance
The delivery class is also analyzed in the extended table maintenance (SM30). The maintenance interface generated for a table makes the following checks:
You cannot transport the entered data with the transport link of the generated maintenance interface for tables of delivery classes W and L.
When you enter data, there is a check if this data violates the namespace defined for the table in table TRESC. If the data violates the namespace, the input is rejected.
We generally use C for customer to enter data into the table
when you change it to Application table (A) you have to regeenrate and to give the access for entering the data
see the table maintenance generator doc
table maintanance Generator is used to manually
input values using transaction sm30
follow below steps
1) go to se11 check table maintanance check box under
attributes tab
2) utilities-table maintanance Generator->
create function group and assign it under
function group input box.
also assign authorization group default &NC& .
3)
select standard recording routine radio in table
table mainitainence generator to move table
contents to quality and production by assigning
it to request.
4) select maintaience type as single step.
5) maintainence screen as system generated numbers
this dialog box appears when you click on create
button
6) save and activate table
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed2d446011d189700000e8322d00/content.htm
http://help.sap.com/saphelp_46c/helpdata/en/a7/5133ac407a11d1893b0000e8323c4f/frameset.htm
/message/2831202#2831202 [original link is broken]
One step, two step in Table Maintenance Generator
Single step: Only overview screen is created i.e. the Table Maintenance Program will have only one screen where you can add, delete or edit records.
Two step: Two screens namely the overview screen and Single screen are created. The user can see the key fields in the first screen and can further go on to edit further details.
<b>Reward points for useful Answers</b>
Regards
Anji

Cannot change Valuation Class although no Open-PO

Dear Gurus,
I try to change Valuation Class in Material Master but I cannot after I created PO and still after MIGO and MIRO.
We are using PS and Material Master is set as below;
Ind./Coll in MPR4 = 1
Since requirement comes from PS, PO is created with account assignment category Q.
Once we execute MIGO and MIRO for the PO, still we cannot change Valuation Class.
If you know the way to change Valuation Class, would you tell me how?
Best Regards,
AK

Hi,
The change of the valuation class will impact on ML (material ledger), if the ML
is active. Is ML active on your system?
The note 575632 explains partly the effects on CCS. The
valuation class is used to allocate the plan costs to the related cost
element. Therefore, it is advisable to create new materials instead of
changing the valuation class. This would be straight forward and easy to
follow-up. The CCS does not a change history. Consequently, the previous
periods can not be explained with current CCS. That may lead
inconsistencies under circumtances. It is up to your decision. You can
change, test the impact and decide on. The proposed solution of SAP
would be avoiding that change and creating new materials.
When you try to change the valuation class, what is the details of the
error?
In order to change valuation class in the material master, you have to
make sure that none of the following exist in you system:
1 Valuated stocks in the current period or in the previous period
2 Open purchase orders or delivery schedule lines
3 Production orders for which a goods movement has already taken place
The system checks the stocks (storage loc. stocks and special
stocks) of the same period in which the valuation class will be changed.
If the valuation class of current period will changed, check in
transaction code MMBE for zero stocks, or in SE16: MARD/MBEW;
MCHB/MKOL/MSKA/MSKU/MSLB/MSPR.
The system checks all dependant purchase documents without delete flag
and error M3368 occurs when it finds at least one non deleted po item
(not only when stocks exist).
1. First be sure that no stocks exist in current AND previous period!
   see note 30656, with an example how to get zero stocks.
2. SE16 ->table EKPO. Select all po items of the related material.
   If you found items with LOEKZ <> 'L', you have to delete them in ME22
3. SE16 ->table AFPO. Select all items of the related material/plant.
   If you find at least one item, change of val.clss. is not possible.
   You have to these production order(s) !
These hard restrictions are necessary as inconsistencies in account
assignment will follow after change of val.class, when proceeding
follow up functions of a PO item before and after changing valuation
class. Also attached is 146241.
In customizing for the Material Master, you can switch the check for
open purchase orders and/or for production orders to a warning.
You do this in Define Attributes of System Messages by assigning
the message type Warning to message MM 326 and/or MM 327 respectively.
Please refer to note 160970 for more information.
I hope this will help you in resolving the reported issue.
Best Regards,
Arminda Jack

Customer table with delivery class 'A' asking for a request

Hello.
I've built an customer table and defined the delivery class 'A' ... Application table (master and transaction data).
Data Browser/Table View Maint. 'X' ... Display/Maintenance Allowed.
Why is this type of table definition asking for a change request to store table entries?
Please, provide some help.
Mário Semedo

Thanks ... how did i let it pass?
Thanks alot!

Data maintenance in a table of delivery class S

Hi,
If i have to maintain en entry in a table with delivery class S (System table, maint. only by SAP) , can i do it in any client
or only system maintenance client.
Regards,
sushant

hi
There are the following delivery classes:
A: Application table (master and transaction data).
C: Customer table, data is maintained by the customer only.
L: Table for storing temporary data.
G: Customer table, SAP may insert new data records, but may not overwrite or delete existing data records. The customer namespace must be defined in table TRESC. (Use Report RDDKOR54 here).
E: System table with its own namespaces for customer entries. The customer namespace must be defined in table TRESC. (Use Report RDDKOR54 here.)
S: System table, data changes have the same status as program changes.
W: System table (e.g. table of the development environment) whose data is transported with its own transport objects (e.g. R3TR PROG, R3TR TABL, etc.).
Behavior during client copy
Only the data of client-specific tables is copied.
Classes C, G, E, S: The data records of the table are copied to the target client.Classes W, L: The data records of the table are not copied to the target client.
Class A: Data records are only copied to the target client if explicitly requested (parameter option). Normally it does not make sense to transport such data, but is supported to permit you to copy an entire client environment.
Behavior during installation, upgrade and language import
The behavior differs here for client-specific and cross-client tables.
Client-specific tables
Classes A and C: Data is only imported into client 000. Existing data records are overwritten.
Classes E, S and W: Data is imported into all clients. Existing data records are overwritten.Class G: Existing data records are overwritten in client 000. In all other clients, new data records are inserted, but existing data records are not overwritten.
Class L: No data is imported.
Cross-client tables
Classes A, L and C: No data is imported.
Classes E, S, and W: Data is imported. Exisitng data records with the same key are overwritten.Classe G: Data records that do not exist are inserted, but existing data records are not overwritten.
Behavior during transport between customer systems
Data records of tables of delivery class L are not imported into the target system. Data records of tables of delivery classes A, C, E, G, S and W are imported into the target system (this is done for the target client specified in the transport for client-specific tables).
Use of the delivery class in the extended table maintenance
The delivery class is also analyzed in the extended table maintenance (SM30). The maintenance interface generated for a table makes the following checks:
You cannot transport the entered data with the transport link of the generated maintenance interface for tables of delivery classes W and L.
When you enter data, there is a check if this data violates the namespace defined for the table in table TRESC. If the data violates the namespace, the input is rejected.
Hope this information is useful to you.
Regards
Vinodh A

About Delivery class

HI All,
In DDIC,in tables the Delivery class 'L' is for what purpose.Explain me about this delivery class
Thanks In Advance

Hi,
Delivery Class
The delivery class controls the transport of table data for installation, upgrade, client copy and when transporting between customer systems. The delivery class is also used in the extended table maintenance.
There are the following development classes:
A: Application table (master and transaction data).
C: Customer table, data is only maintained by the customer.
L: Table for storing temporary data.
G: Customer table, SAP may insert new data records but may not overwrite or delete existing ones. The customer namespace must be defined in table TRESC. To define the customer namespace use report RDDKOR54. You can start it directly from the table maintenance by choosing Customer namespace definition on the Attributes tab.
E: System table with its own namespace for customer entries. The customer namespace must be defined in table TRESC. To define the customer namespace use report RDDKOR54. You can start it directly from the table maintenance by choosing Customer namespace definition on the Attributes tab.
S: System table, data changes have the status of program changes.
W: System table (e.g. table of the development environment) whose data is transported with its own transport objects (e.g. R3TR PROG, R3TR TABL, etc.).
Behavior during Client Copy
Only the data of client-dependent tables is copied.
Class C, G, E, S: The data records of the table are copied to the target client.
Class W, L: The data records of the table are not copied to the target client.
Class A: Data records are only copied to the target client if explicitly requested (parameter option). It normally does not make sense to transport such data, but this is supported nevertheless to permit the entire client environment to be copied.
Behavior during Installation, Upgrade and Language Import
The behavior of client-dependent tables differs from that of cross-client tables.
Client-Dependent Tables
Class A and C: Data is only imported into client 000. Existing data records are overwritten.
Class E, S and W: Data is imported into all clients. Existing data records are overwritten.
Class G: Existing data records are overwritten in client 000. In all other clients, new data records are inserted, but existing data records are not overwritten.
Class L: No data is imported.
Cross-Client Tables
Classes A, L and C: No data is imported.
Classes E, S, and W: Data is imported. Existing data records with the same key are overwritten.
Class G: Non-existent data records are inserted, but no existing data records are overwritten.
Behavior during Transport between Customer Systems
Data records of tables having delivery class L are not imported into the target system. Data records of tables having delivery classes A, C, E, G, S and W are imported into the target system (for client-dependent tables this is done for the target clients specified in the transport).
Use of the Delivery Class in the Extended Table Maintenance
The delivery class is also used in the Extended Table Maintenance (SM30). The maintenance interface generated for a table makes the following checks:
It is not possible to transport the entered data using the transport connection of the generated maintenance interface for tables having delivery classes W and L.
Data that is entered is checked to see if it violates the namespace defined in table TRESC. If the data violates the namespace, the input is rejected.
Regards,
Jagadish

Delivery class

which purpose we use DELIVER CLASS plz tell me in
general terminalogy.not in technical

Hi,
Delivery class is the one which controls the table, while upgrading, maintaining and copying.
The delivery class controls the transport of table data when installing or upgrading, in a client copy and when transporting between customer systems. The delivery class is also used in the extended table maintenance.
There are the following delivery classes:
A: Application table (master and transaction data).
C: Customer table, data is maintained by the customer only.
L: Table for storing temporary data.
G: Customer table, SAP may insert new data records, but may not overwrite or delete existing data records. The customer namespace must be defined in table TRESC. (Use Report RDDKOR54 here).
E: System table with its own namespaces for customer entries. The customer namespace must be defined in table TRESC. (Use Report RDDKOR54 here.)
S: System table, data changes have the same status as program changes.
W: System table (e.g. table of the development environment) whose data is transported with its own transport objects (e.g. R3TR PROG, R3TR TABL, etc.).
Behavior during client copy
Only the data of client-specific tables is copied.
Classes C, G, E, S: The data records of the table are copied to the target client.
Classes W, L: The data records of the table are not copied to the target client.
Class A: Data records are only copied to the target client if explicitly requested (parameter option). Normally it does not make sense to transport such data, but is supported to permit you to copy an entire client environment.
Behavior during installation, upgrade and language import
The behavior differs here for client-specific and cross-client tables.
Client-specific tables
Classes A and C: Data is only imported into client 000. Existing data records are overwritten.
Classes E, S and W: Data is imported into all clients. Existing data records are overwritten.
Class G: Existing data records are overwritten in client 000. In all other clients, new data records are inserted, but existing data records are not overwritten.
Class L: No data is imported.
Cross-client tables
Classes A, L and C: No data is imported.
Classes E, S, and W: Data is imported. Exisitng data records with the same key are overwritten.
Classe G: Data records that do not exist are inserted, but existing data records are not overwritten.
Behavior during transport between customer systems
Data records of tables of delivery class L are not imported into the target system. Data records of tables of delivery classes A, C, E, G, S and W are imported into the target system (this is done for the target client specified in the transport for client-specific tables).
Use of the delivery class in the extended table maintenance
The delivery class is also analyzed in the extended table maintenance (SM30). The maintenance interface generated for a table makes the following checks:
You cannot transport the entered data with the transport link of the generated maintenance interface for tables of delivery classes W and L.
When you enter data, there is a check if this data violates the namespace defined for the table in table TRESC. If the data violates the namespace, the input is rejected.
Regards,
Satish

Error Message V1810 - Make to Order No Change delivery plant in Sales Order

Hello, for a client where I'm setting the flow intercompany , but i have an error on the Sales Order when I must be change delivery plant.
Scenario: Make to Order, Product configuration, Sales Order BOM created by CS60
Step:
1 - I create sales order fo company X delivery plant 1000
2 - Creates Order BOM on plant 2000 Company Y
3 - creates MRP Planned Order
4 - Convert Planned Order to Production Order
For different issues can happen that you decide to ship the goods to a different plant than the X. Production Plant remains 2000.
If I try to change the plant on the Order system stops me with the following error:
Message V1810 - Plant can no longer be changed
Diagnosis
The plant can no longer be changed in the Following situations:
The item has been assigned to a project.
There is a production order for the order item but it is not a staticassembly order.
Already have accrued costs.
For the very complex structure of the product I can not delete the production order and sales order BOM.
How do I handle these cases?
Can anyone help me?
Best regards
Giuseppe

Hi Guiseppe,
can you please answer some questionsa to understand your requirement.
if you want to transfer the goods from plant to plant you can do it through Stcok transfer MB1B t code.
1.then why you want to change the plant? in which element you are trying to do in sales order or production order?
2.you mention it as intercompany and MTO can you be clear for whoom you got the sales order(internal or External Customer?

Changeing Valuation class-what happens to deleted open docs.

Hello,
we are planning to change the valuation class for material. In order to change the class we would have to delete all open items that trace back to the material (PO, GR, IR). I run me2m to identify the open documents for that material.
My issue is when I reverse or delete the IR, GR, and PO what happens to the those documents.? We have documents that go back to 2007.
Do we have to recreate the PO, GR, IR after we change the class.?What are the long term effects when doing this change (Audit)?
Please advise.
Thanks.

You don't need to worry about old documents as long as they are not open.
You just need to invoice out all the open GRs or cancel all those GRs. In case of POs, you have to ensure the GR qty is equal to IR qty for each PO line, then you can mark the line as deleted so that the system will allow you to change the val. class. You also need to make the stock to zero.
Once val. Class is changed, you can undo all the above.

How can we change delivery document while doing shipment

Hi all,
How can we change delivery document in background while changing shipment document.My requirement is to change the netweight in delivery while doing shipment.Actually it gets blocked when we open the shipment.
Thank You,
Regards,

Hi,
if you have done the PGI(Post Goods Issue), you can't change the delivery.
If you want to change the devlivery Qty, you should create the delivery with Partial Split (= X) and you can deliver the splitted qty with a new delivery.
Regards,
Baburaj

How to change delivery block for all item in the schedule lines via va32

dear sap expert:
i onle can change delivery block for one sales order item in the schedule line every times via va32,it will take so many time because there are hundreds of item in a sceduling agrrement. how to change all the item one times.
please give me a way to resovle the problem.
best regards.

dear:
the fast change function cann't resovle the problem,i first double click the item of schedule agreement ,then select the schedule lines option, finally in the delivery block input the reason of bolck.
best regards.

How to change delivery date (LFDAT) in me57 item data

hi ,
While Creating purchase order (me57) . on the basis of info rec   . i want to change delivery date by
passing info rec to table eine and get field aplfz .
then adding aplfz to sysdate    and pass it to
Delivery date   .
i have done this using USER EXIT EXIT_SAPMM06E_016
and modified table teket with field eindt   but still in screen fields it shows old date value   .
After Debugging i found that that it passes value from internal table ETT[] .
how to modify internal table ETT[] which is used to display data on screen   .
regards
Deepak.
Edited by: Deepak Dhamat on Jun 8, 2011 8:32 AM
Edited by: Deepak Dhamat on Jun 8, 2011 10:35 AM

hi ,
i have implemented BAdi me_process_po_cust
for changing Delivery date   .
method if_ex_me_process_po_cust~process_item .
data : eeind_dt type eket-eindt ,
         t_aplfz type eine-aplfz ,
         delivery_dt(10) type c.
ls_item = im_item->get_data( ) .
if sy-tcode = 'ME21N' .
    select single aplfz into t_aplfz from eine
      where infnr = ls_item-infnr .
    if sy-subrc = 0 .
      if t_aplfz is not initial .
        eeind_dt = sy-datum + t_aplfz .
        concatenate eeind_dt6(2) eeind_dt4(2) eeind_dt+0(4) into delivery_dt .
      endif.
    endif.
    ls_item-eeind = delivery_dt .
    call method im_item->set_data
      exporting
        im_data = ls_item.
    clear : delivery_dt ,t_aplfz ,eeind_dt .
endif.
regards
Deepak.

Change Delivery date in Sales Order

Hi all
I want to change Request Delivery Date in Sales Order. But when I changed Request Delivery Date system appear" The default date is not copied into existing schedule lines"
And Delivery Date didn't change.Could you tell me how to change Delivery Date ?
I setup Request Delivery Date - September 21th but Availability Date is September 19th. Could you tell me how to setup loading time, picking time, packing time ?
Thank and Best regards,
Thang

Hi,
When you change the Request Delivery Date, it automatically changes the schedule line date of all the materials, but by default does not change the schedule line date of the ordered material.
So just check the ordered material schedule line date and change it manually in the order.
Similarly maintain the same date in all the resp fieldsi in the delivery, wherever you see the date.
Regards,
Siddharth.

Change delivery block in order schedule line

I use badi "BADI_SD_SALES" method "SAVE_DOCUMENT_PREPARE" to change delivery block in schedule line. I change field fxvbep-lifsp and I change table fxvbep the I add or I change line in table fyvbep. It work fine when I create the order but not when I make a change. May be I have to use another exit.
Help required,

Hi Daniel,
In change mode.. (Mean when you change the sale order).. Just do the changes in FXVBEP table only.
As per my knowledge, The FX*** and FY*** are used to find the delta changes in the document and these changes will get updated in change document history and the same will be updated in database.
In the change mode, when you do the changes to both the tables, the delta will not be there and may be the delivery block not updated.
Try doing change in FX table only.
Regards,
Sai

How to change Valuation class in material master(have stock)

HI,
I would like to change the valuation class in material master, How to change VC? is there any process before changing VC?
I heared when Material have nil stock then only it's possible to change VC, Is it correct? which TC can I use for change VC?
Regards,
venki

Dear venki,
To change Valuation class you must have zero stock in the current period, and zero stock at the end of the last period, plus no open PO lines . flag for deletion all open PO lines,
Regards
shankar

Change Delivery Class of ZTable

Similar Messages

Maybe you are looking for