What is the "shell creation" in TDMS?

I cannot find the exact definition of above term "shell creation". Would you please help? Thanks!

In TDMS, there are different ways of selecting data from the production server. So there are different Process Types.
Shell Creation is one of those types.
SHELL CREATION- Migrated data contains only cross-client data and the required client-specific user and address data, but no other client-dependent data.
Hope this answers your question

Similar Messages

What is the "Content Creation with Final Cut Studio" ?

Hi,
How does this category differ from Final Cut Studio?
Thanks for your time.

Hi:
Check this thread:
http://discussions.apple.com/thread.jspa?messageID=4606811
Hope that helps !
Alberto

TDMS 3.0 for ERP 6.0: step by step procedure for TDSH6 Shell creation

Dear All,
I need to perform shell creation. I have never done this and need help with step by step instructions.
I need to refresh my my development system with a TDMS shell creation from production client in production system.
I am familiar with TDTIM and performed many TDTIM copies. I have gone throught the master and operational guides for TDMS also.
I would try to list down my understanding so far after reading the guides.
Please correct me if I am wrong ang also suggest correct steps.
1. All my three systems (central, sender and receiver) are ready from installation point of with with authorizations and latest SPs.
2. I log into Central/Control system and start a new package "ERP Shell creation package for AP Release higher 4.6 "
3. AS I have never executed this option I do not know what are the stps inside it.
   But I assume I should be asked for the source client details from which shell needs to be creates. (000 or pruduction client)
   What type of shell : slave or master?
4. During the shell creation from sender system client, is there a downtime for sender system.
5. Once the shell creation is done an export dump will created.
6. I perform all the preprocessing steps of a homogenous system copy on the receiver systems.
7. Stop receiver system, start sapinst database instance installation with homogenous system copy with R3load option.
8. Provide the export dump location to sapinst.
9. After database instance is installed, perform system copy specific post processing steps.
10. Afte the system is ready it has only one client 000 now available in development system and i need to create a new cleint from 000 which will act as my new development cleint.
I request all you experts to please provide your comments at the earliest as activity would be starting from 5th of this month.
Regards,
Prateek.

Hi,
Let me answer your questions.
Some queries
1. Is there a downtime for Production system (sender system).
   SAP recommends that nothing much should be going on during the export of the Sender(PRoduction) system, but so far i have never encountered an issue doing the export in online mode.
2. Shell creation works on both Production and 000 client or only Production client,
   Be carefull!!! - A Shellcreation is a normal Homogenous Systemcopy using R3load. You will create a 'new' system with the DDIC and clientindependent customization of the Sender system. ALL former data of the target system will be deleted.
You mention that you will refresh a development system that way. Please be aware of the implications that a development refresh contains. That said. After the refresh you will have the 000 client and parts (users ... authorizations of sonder) of the other clients on the new system.
3. when I import the the dump using sapinst, how many clients are available in receiver systems.
See above. All client configuration will be available, but nearly no data will be in these clients except 000. A manual part of the Shellcreation is to clean up the target system (delete the clients that are not needed) This is a fast process.
4. Soem where in the guide it is mentioned that downtime depends on the type of shell I create.
Kindly suggest should I create a master shell or slave.
Hm. The master shell is just a concept that you create a complete new system and put that system into your transport landscape without filling it with data. You can then use that system as the source for a normal (database dependent) systemcopy without impacting your prod system. The result is a very small copy that can be repeated very often without an impact to prod/QA...
Downtime is as described in point1 not required
5. Once I execute this activity of shell creation for lets say receiver system A, then can I use the same export dump for second receiver system B.
Yes
6. Lastly please suggest the activity execution time as customer has provided us 2 days to execute this activity.
This depends on your knowledge of homogenuous systemcopies and the preparation + some items like size of stxl and other tables that will be exported/imported. If you are very familiar with the systemcopy process using R3Load 2 days are feasable.
I have seen shellcreations done within 1-2 days but also much longer ones!
As a prerequisite i would always recommedn to have the latest R3* + migmon exe available on sender + target.
I hope i have clarified some of your items.
Best Regards
Joerg

TDMS for BI - shell creation and SMIGR_CREATE_DDL

If a homogeneous system copy of a BI system is done, it's necessary to run the job SMIGR_CREATE_DDL because depending on what database is used, special SQL scripts for tables must be used (concerning primary keys).
How does that integrate into a shell creation? Is the shell creation process aware of those scripts? I mean, it's theoretically possible that the SQL scripts has a table that is excluded from being transferred?
Markus

Markus and Pankaj:
I have created a SHELL (BW) using Markus' way as listed below.
Because Markus did not mention that SMIGR_CREATE_DDL should be run at the beginning, so I did not run it.
So how to determine in the created shell what is missing?
We do have partitioned tables and bitmap indexes.
Thanks!
Here is the way provided by Markus:
I basically do shell creation as follows:
- install the latest system copy tools (R3load, R3ldctl, R3szchk, libdb<database>slib.dll)
- create an installation directory and give full permissions to <sid>adm and SAPService<SID>
- create a directory for export location and give full permissions to <sid>adm and SAPService<SID>
- open a cmd.exe as <SID>adm, step to the installation directory and execute "R3ldctl -l R3ldctl.log -p ." (note the "dot" which means actual directory)
- in parallel start the client export of client 000 in source system using SCC8 (profile SAP_ALL) and note the file names you get in the last dialog window
- when R3ldctl is finished give permissions to SAPService<SID> for all files in the installation directory
- proceed with TDMS
- when you are at the point to start the system copy start sapinst, choose system copy and select start migration monitor manually (VERY important!)
- sapinst will run R3ldctl, R3szchk and then prompts you to start migration monitor
- step to your normal installation directory (c:\program files\sapinst_instdir....), open export_monitor_cmd.properties and adapt the file. The import thing is, that you need to point to YOUR DDL<DB>.TPL file you create in step 4 (in my list here)
- start export_monitor.cmd and export the system
- proceed with TDMS to adapt the database sizes (DBSIZE.XML)
Import:
- if you have an already installed system uninstall it
- start sapinst normally, choose system copy and point to the export you created
- install the system normally (as a new installation)
- if you want to make sure the import works as the export choose "start migration monitor manually"
- if sapinst stops and requests you to start migration monitor copy the kernel from source system to target system
- configure import_monitor_cmd.properties and start migmon
- logon in client 000, start transaction STMS and create a domain (basically only a transport profile will be created)
- start program BTCTRNS1 (this will suspend all jobs from the source system but not delete them)
- copy the files from the client copy to TRANSDIR/cofiles and TRANSDIR/data and import them to client 000 (either use STMS or use command line tp)
- adapt profile parameters (RZ10)
- run SGEN
- invalidate connections in SM59 that point to other production systems
- finished
- to re-enable all the jobs run BTCTRNS2, however, I'd do this only if you're sure you have invalidated RFCs and or sending jobs (e. g. from SCOT)

Shell creation issue

Dear experts, I've got a question regarding shell creation of TDMS.
I've finished the export from ECC IDES system (SR3). The size of export files are over 30GB... is it normal? Can I reduce the data? Since it'll take me more than 200GB disk in target system.
Is it been setup in the step of "Determine Tables to be Excluded from the Export"?
Which data can be reduced in the table regarding IDES shell creation?
Thanks!

Hi Jett
Your first question is not very clear to me -
Seems that, the data folder of export is still the same as before. Is it normal?
>I think you mean to say that the size of the data folder of export is of same size as before. Yes that is normal. However i feel the doubt that remains in your mind is that you want to be sure that its doing a reduced transfer and not a full transfer. Well you cant make a decision based on the size of the export folder. To decide that you can do the following -
Pick one excluded table and in the exports folder try to search for its existence in the .TOC files. If you find it in any of the .TOC files then it indicates that a full transfer is happening instead of a reduced one. If you dont find it in .TOC but you find that excluded table in .STR files that indicates that a reduced transfer is happening and everything is fine. The existence of the excluded table in .STR file indicates that the structure information of the excluded table will be transferred although the data is not getting transferred.
Regarding your second set of queries -
Please understand that there are two parts to shell creation one is excluding the data to be transferred for a set of tables, so no data at all get transferred to the target system for all the excluded tables. Second part is that how much filespace (on target system) should be allocated to tables which are there in the excluded tables list, by default the import process will assign same space to a table in target system as the space allocated to it in the source system. So if a table for which no data is getting transferred was of size say 10 MB in sender so the import process will allocate a filesize of 10 MB to the table in target system also although it will be blank. To avoid this and to reduce the overall size of target system, we reduce the sizes that should be allocated to the excluded tables in the target system in the activity "Determin and Modify Size of Tables".
Now for the question what do the ratios mean and on what basis do we assign the ratios-
>Say for example Ratio20 means that the import process will assign 20% of the original size (in sender system) to the table in the target system. Regarding on what basis are the ratios determined - The ratios are determined on the basis that how much data do you expect each table to hold later on. So this depends on which process of TDMS (vis TDTIM, TDMDC, TDTCC) do you want to execute after shell creation. In case of TDTIM process type it may also depend on the period for which you want to transfer the data. For this reason we have provided various templates (vis TDTIM, TDMDC etc) in the activity "Determin and Modify Size of Tables". So we have tried to build this intelligence into the system. So if you want to excute a TDMDC scenario after shell creation then you should choose the template TDMDC in the activity "Determin and Modify Size of Tables" and the system will automatically assign defferent ratios to different tables.
In my last post i had suggested that if you want to further reduce the size of your target system (although the assigned template will automatically reduce the size of the target system) you can do the same by further reducing the ratios for the tables for which you dont expect much data to be transfered. This functionality of altering ratios for certain table or set of tables is available in the activity "Determin and Modify Size of Tables". SAP already delivers ratios which will be optimum for different tables, if you want to override those setting and provide your own ratios then it should be done at your own risk.
I hope this post explain you the entire concept. In case you have some doubt feel free to write again.
Regards
Pankaj.

What is the "BW shell creation package for BW system" in TDMS?

I see for lower version of SAP systems such as 4.6 and BW(e.g.3.0, etc), there is a "shell creation package " for those
types of systems.
Could you explain what is that for?
Thanks!

1) where to find the info about the copy sequence such as: first shell creation, then initial package or whatever, then ...?
> TDMS solution operation guide will be helpful, the same is available at SAP service market place. In short the sequence is -
first shell (only if the repository is not in sync) then initial package (ex. TDTIM) and then refresh packages (as an when needed)
2) for HR we do not have shell creation, what we have is "initial package for master data and customizing" , the next step is "ERP initial package for HCM personel dev. PA & PD". Why we do not have shell creation here?
> For HR as only few objects are transfered the need of a full shell system does not arise. only the object to be transfered are synced.
3) Will TDMS replace system copy for ERP, BW, CRM completely?
> Shell will not replace them but we may say that it will supplement it. When you need a complete copy means repository along with application data then you need to go for system copy but if you only need repository to be copied from source to destination then shell is helpful. Also it should be noted that Shell is an TDMS package whereas System copy is a SAP standard tool.
I hope the above response is helpful.
Regards,
Pankaj

SAP TDMS System Shell creation

Hello,
I am new to SAP TDMS. I want to know about System shell creation.
Is System shell used to create a totally "new system" or can it be done on an existing system? Can it be done on an existing system by using a separate client??
If we use existing system what happens to its already present data. As per the Operations guide it says we need to do a Homogeneous system copy by using TDMS tools.This will delete the data in existing system.So does it mean all database content will be deleted or only the client specific data?
Many Thanks.
Ravindra

You can get more details from the following documents:
Operations Guide
http://service.sap.com/instguides -> SAP Components -> SAP Test Data Migration Server -> TDMS 3.0
Security Guide
http://service.sap.com/security -> Security in Detail -> SAP Security Guides -> SAP Test Data Migration Server

TDMS shell creation

Is TDMS shell creation for the ABAP stack only?
What happens in the ABAP+Java systems?
Thanks,
Sri

Hi Pankaj,
I don't think TDMS is meant for JAVA. At preset It is only meant for ABAP stack to transfer data using different senarios.
You can transfer the data from source and at the same time the Java settings in the target remain the same.
Thanks,
Sridhar

Is an existing client the only prerequisite for shell creation?

I am preparing my first shell creation. From what I read, I get the impression that an existing client is
the only prerequisite for a shell creation. I already created the CPIC user and installed DMIS_ on the sender and central systems.
Could you confirm? Thanks!

TDMS Shell is a form of system copy where you copy an existing source system into a target system but only the non-application related data. TDMS Shell is a prerequisite for other TDMS processes.
Regarding prerequisites for Shell - all prerequisites and preparation that apply to SAP system copy apply for Shell also. Refer to SAP system copy guide for the same.
Best regards
Pankaj

Migration monitor in TDMS shell creation

Hi,
I am working on a TDMS shell creation for ECC system, I have few question..
1) Is it mandatory to run migration monitor manually while in both exporting and importing database with R3load option in tdms shell creation or only while running R3load export?
2) How to run export monitor activity in background?
3) How to parallel R3load processes to export a single package instead running one r3load for each package?
OS: AIX
DB: DB2
SAp ECC 6
Thanks
Praveen

Answers to your questions are below -
1) It is mandatory during the exports of data from the source system.
2) It should not be run in background
3) Use table splitting using R3TA, but that should be done before exports.

TDMS shell creation - R3szchk running longtime

Hi,
I am running a shell creation package, in Export ABAP phase R3szchk running long time and there is nothing written to log file
-rw-r----- 1 root sapinst 0 Oct 4 19:56 /tmp/sapinst_instdir/ERPEhP4/LM/COPY/DB6/EXP/CENTRAL/AS-ABAP/EXP/R3szchk.exe.log
where else I can check to find out the issue?
Thanks
Din

Thanks Pankaj for the valuable information.
---The size of exports may depend on the data in your client independent tables. There are certain client indepedent table which hold a lot of data for example STXL, STXH and DYNP* tables. It also depends on the volume of custom development that you have done in your systems. Most of the client independent tables are exported in full duing shell.
I could understand that. I ran an optional activity u201CCheck size of large tables (optional)u201D in TDMS Shell package, it returns witj some large tables, such as
STXH- 190,854,900 KB
STXL- 26,819,840 KB
DYNPSOURCE- 20,452,251 KB, some of these are independent and some are dependent tables. For ex. STXH is dependent table with size 190GB, does it means that this table will be exported in full during shell export?
However, you need to be sure that because of certain mistakes you are not exporting the complete system (including application data). As stated by Marcus, you need to make sure that you are using Migration monitor in manual mode and that you configure the Migration monitor control file with correct parameter values.
I think I configured import monitor control file correctly and started it manually.
Here is the import monitor startup log:
Export Monitor is started.
CONFIG: 2011-10-05 00:49:22
Application options:
dataCodepage=4102
dbType=DB6
ddlFile=/shell_install/DDLDB6.TPL
ddlMap=
exportDirs=/shell_export/ABAP
ftpExchangeDir=
ftpExportDirs=
ftpHost=
ftpJobNum=3
ftpPassword=*****
ftpUser=
host=
installDir=/shell_install
jobNum=6
loadArgs=
mailFrom=
mailServer=
mailTo=
monitorTimeout=30
netExchangeDir=
orderBy=name
port=
r3loadExe=
server=
taskArgs=
trace=all
tskFiles=yes
Thanks
Din

What are the mandatory fields while creation of material master in differen

what are the mandatory fields while creation of material master in different views?

Hi Gopi,
This is purely depends on the function configuration, which would be done MM consultants. Kindly check with them.
thanks & regards
Kishore Kumar Maram

TS3775 Hi I am trying to connect my mba mid 2011 with an imac 27" 2011 with target display mode tdm. When I am using a thunderbolt cable nothing will work. When I use a minidisplay cable, both screens turn blue but eventually nothing happens. What is the

Hi I am trying to connect my mba mid 2011 with an imac 27" 2011 with target display mode tdm. When I am using a thunderbolt cable nothing will work. When I use a minidisplay cable, both screens turn blue but eventually nothing happens. What is the problem

Your answer is likely in Target Display Mode: Frequently Asked Questions (FAQ) - Apple Support If you are familiar with this document, please re-read it and I suspect you may find something you either missed or are doing incorrectly.

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
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.
Regards
Eswar

HT4910 documents edited on iphone, ipad, & mac what is the order of creation and editing and must each change be manually initiated to update the icloud

documents edited on iphone, ipad, & mac what is the order of creation and editing and must each change be manually initiated to update the icloud?

No idea what you mean by the firsy part of your question.
Documents edited on the Mac need manually uloading to iCloud at iCloud.com,documents edited on the mobile devices are updated automatically.

What is the "shell creation" in TDMS?

Similar Messages

Maybe you are looking for