What are the pre requisites for SPLIT VALUATION OF A MATERIALS

Dear friends
What are the pre requisites for creating SPLIT VALUATION for A MATERIAL in particular Plant
regards
Radha

Hi,
I am not sure what you mean exactly.
But you would need to have the valuation category and all of the valuation types created in config in advance.
Then you can allocate the appropriate valuation category to the material (accounting view) (as long as no stock or open POs etc. exist).
then you can create your additional accounting views (one for each valuation type that you want to use).
Steve B

Similar Messages

What are the pre requisites for implementing ChaRM

Hi
We are planning to implement ChaRM & CTS+ in our organization. We are using three system landscape and we have EP, PI, BI and ECC systems.
Can you please tell me what are the pre requisites for implementing ChaRM & CTS+ and what are the areas i need to look before starting the configuration
Thanks & Regards
Anand

The listed pre-requisites for the implementation of ChaRM are;
1. Already completed the basic configuraiton of SAP Solution Manager
2. You have set-up your solution, landscape and installed base (iBase) for the systems to be integrated
3. you have setup business partners for the users (or at least 1)
4. satellite systems are at the minimum support package level required (note 907768)
5. connections are available to the satelite systems
6. CTS+ if you wish to control non ABAP change requests through ChaRM

What are the pre-requisites for learning OA Framework?

Hi,
Im new to oaf,can any body help on this
What are the pre-requisites for learning OA Framework?
Karthik

In order to develop any OAF Application you need to know few concepts before doing any kind of development. The concepts are basically the Business Components for Java(BC4J) components.
They are:
Application Module(AM)
Entity Object(EO)
View Object(VO)
Association Object(AO)
View Link(VL)
Now let us see the description of each component.
Application Module:
Application Modules serve as a containers for related BC4J components. The pages are related by participating in the same task. It also defines the logical data model and business methods needed.They provide the transaction context and also used for establishing database connection. AM’s can be nested to provide more complex AM’s.
Entity Object:
EO encapsulates the business logic and rules.EO’s are used for Inserting,Updating and Deleting data. This is used for validating across the applications. We can also link to other EO’s and create a Association object.
View Object:
View object encapsulates the database query. It is used for selecting data. It provides iteration over a query result set.VO’s are primarily based on Eo’s. It can be used on multiple EO’s if the UI is for update. It provides a single point of contact for getting and setting entity object values. It can be linked together to form View Links.
Association Object:
An association object is created where we link EO’s. For example take the search page where we link the same EO to form a association between the manager and employee. Every employee should have a manager associated. But if it President then no there is no manager associated. This is a perfect example to understand the AO.
View Link:
A view link is an active link between view links. A view link can be created by providing the source and destination views and source and destination attributes. There are two modes of View link operation that can be performed. A document and Master/Detail operation.
-----Let me know if you need more information
Regards
Meher Irk
Edited by: Meher Irk on Oct 23, 2010 10:45 AM

What are the pre requisites for E-Recruitment module?

Hi all,
What are the pre requisites for implementing E-Recruitment module ?
Does it require Hr module or as stand alone it can work?
Regards.
Rajendra

Thanks Aniket
Will the following configuration work as e-recruitment stand alone mode.
WAS with ABAP stack + E-Recruting 6.0 sp + Java stack + Portal + ESS MSS Business package ( for e recruiting).
Regards
Rajendra

What are the pre requisites for SAP SRM7.0 DB Rrefresh?

Hi,
What are the pre requisites for SRM DB Rrefresh?
Thanks

Hello Peter,
When it comes to DB refresh you need to know what all the client dependent data which needs to be retained.
For example you need RFC connections, Variants, User master etc.
As a pre task of Database refresh you may need to export the tables which are related to this so that once the database is refreshed you need to import them.
Ensure the proper backup of production database is available. Also check all the STMS configurations which need to be retained again.
Make sure that you need to have enough disk space which can accommodate your production data in to the pre production system.
These are some of the general consideration one needs to have but again it depends on the environment on which one runs SAP systems.
Regards
Vivek

What are the pre-requisite for JAVA Proxy communication?

What are the pre-requisite for JAVA Proxy communication?

Hi,
You can install the Java proxy runtime on the SAP J2EE Engine Release 6.40 SP5 or higher.
The messaging system that the Java proxy runtime uses to send messages to the Integration Server must also be installed on the J2EE server.
To send messages from a J2EE application, the application must be programmed against beans that encapsulate all details about the Java runtime. The following classes are generated:
· Proxy classes that send or receive messages using the Java proxy runtime.
· Bean classes as an outer shell that conform to the J2EE standard. The beans call the proxy classes for communication.
The classes must be deployed on the J2EE server together with their J2EE application
see this link for the example scenario http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d

What are the pre-requisite for ABAP Proxy communication?

What are the pre-requisite for ABAP Proxy communication?

hi,
How to create proxy.
http://help.sap.com/saphelp_nw04/helpdata/en/14/555f3c482a7331e10000000a114084/frameset.htm
How to Activate Proxy.
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
ABAP Server Proxies (Inbound Proxy)
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
OutBound Proxy (Client Proxy)
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
File to R/3 via ABAP Proxy with good example
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
Debug your inbound ABAP Proxy implementation
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
http://help.sap.com/saphelp_nw2004s/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/frameset.htm
Synchronous Proxies:
Outbound Synchronous Proxy
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2boutbound%2bprogram%2b-%2bpurchase%2border%2bsend
Inbound Synchronous Proxy
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2binbound%2bprogram%2b-%2bsales%2border%2bcreation
regards
srinivasreddy

What are the pre requisites for Oracle B2B

Hi -
Could some one share me the sample tutorial for EDI transactions using B2B.
The documents and the threads which i checked does not have complete and basic knowledge for B2B developer.
My requirement is like ,i have an EDI transaction 214 ecs/flat file which needs to be converted to XML file through b2b and the corresponding artifacts can be used by SOA component(BPEL or mediator) to process the output xml further to complete the integration.
Kindly help me with .
Thanks in advance,
Rohini

Hello Peter,
When it comes to DB refresh you need to know what all the client dependent data which needs to be retained.
For example you need RFC connections, Variants, User master etc.
As a pre task of Database refresh you may need to export the tables which are related to this so that once the database is refreshed you need to import them.
Ensure the proper backup of production database is available. Also check all the STMS configurations which need to be retained again.
Make sure that you need to have enough disk space which can accommodate your production data in to the pre production system.
These are some of the general consideration one needs to have but again it depends on the environment on which one runs SAP systems.
Regards
Vivek

What are the Pre-requisite to set Deletion Flag for Maintenance Order ?

Hi Gurus,
              Pls give me what are the pre- requisite to set the deletion flag.
              I want to set deletion flag to some Maintenance Orders which are with notification, but deletion flag - SET,RESET Indiacaors are inactive.
              Following are my observations-
              1) Order is not yet released.
              2) No actual Cost is with the order.
              3) No PR and POs are with the Order.
Pls guide me.
With best regards,
narendra

hi
you can put the deletion flag only when the order has the status CLSD or the balance of the order must be Zero
you can refer the following link
http://help.sap.com/saphelp_47x200/helpdata/en/8d/3e65a0462a11d189000000e8323d3a/content.htm
regards
thyagarajan

What are the Pre-requisites in installing NWDI

Hi Experts,
I would like to ask if you have a list of all requirements when installing NWDI.
Thanks,
Edy

Hi,
no need to do anything with NWDI if you have already one. Or if you are about to install a new one, it can be any version (general recommendation, the higher the better, but if it is say 730 for instance, it'll be able to serve any developments, let it be 700, 710 ... 740, etc. If it is 700 higher than SP13 then again, you'll be able to develop/deploy for any releases. Just make sure it is not lower than SP13 if you intend to use 700 NWDI. If you use higher release than 700 then it does not matter).
I am sure you'll love this blog:
NWDI vs. NWDI content
Cheers,
Ervin

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

What are the pre-requisistes before stepping into MI?

Hello All,
Am gonna start learning SAP MI on few days now.
Wanted to know what are the pre-requisistes before learning this technology?
In other words, is it a must to know J2ME & XML very well?
Awaiting Reply.
Thanks and Warm Regards,
Ritu

Hi Ritu,
For MI applications , we have to do application component developments in both ABAP and Java.
In general MI Application = Java Component + ABAP component.
Java component means , which is running on the client device , we are accessing the MI applicatiion throught the Java component .
For running this Java components , we need proper runtimes.
Currently we have JSP Runtime and AWT Runtime .
JSP Runtime supports JSP applications and , AWT Runtime supports AWT applications.
If u have basic knowledge for application developments in JSP and AWT , then no problem with Java component development.(there is no need to know in detail about J2ME and XML).Basic knowledge of XML is necesssary for Client side application development.
Refer these helps for Client Side application development.
What is SAP Mobile Infrastructure?
http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/gettingstarted/introduction/what_is_me.html
Client runtime
http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/gettingstarted/introduction/what_is_me.html#runtime
SAP NetWeaver Developer Studio and MI Support
http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/eclipse/guideeclipse.html
MDK Plug-in Configuration
http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/eclipse/eclipsemdkwizardsconfiguration.html
New Mobile Infrastructure Project
http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/eclipse/newmeproject.html
Tips and Tricks using the MDK Plug-in
http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/eclipse/eclipsetipsandtricks.html
http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/appdev/smartsync/app_dev_process.html
http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/tutorials/smartsync/definingsyncbo.html
http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/eclipse/newsmartsyncproject.html
For MI Applications , as i mentioned earlier one ABAP part is also there.. Knowledge of ABAP , RFC and BAPI is necessary for Back end application developments(for BAPI Wrapper Creaion and Sync Bo Creation).
refer these links for Back end application development
What is a BAPI Wrapper ?
http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/appdev/smartsync/what_is_a_bapi_wrapper.html
Developing a simple Smart Sync Application
http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/tutorials/smartsync/definingsyncbo.html
http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/appdev/smartsync/defining_syncbo.html
http://help.sap.com/saphelp_nw04/helpdata/en/a6/c32a89005ab2449cf95e5b0731ee40/frameset.htm
http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/appdev/smartsync/bapi_wrapper_types.html
and refer these forums also...
Re: Sample BAPIs for simple two way synchronization
Re: Creating a sample Mobile Sales Application
How to develop a mobile application using netweaver developer studio
Regards
Kishor Gopinathan

What are the CSS selectors for the FireFox 4 Main Menu?

What are the CSS selectors for the FireFox 4 Main Menu?
[http://img228.imageshack.us/img228/5512/ff4menubar.gif http://img228.imageshack.us/img228/5512/ff4menubar.gif]

Still the same as in Firefox 3.5 and 3.6 versions:
<pre><nowiki>#main-menubar
#file-menu
#edit-menu
#view-menu
#history-menu
#bookmarksMenu
#tools-menu
#helpMenu
</nowiki></pre>

What are the field names for below mentioned

Hello Friends
What are the fields names for below tables
in EKKO
Purchase Document Date
Net Value of the purchase document.
In EKPO
Item Description
From which place We bought it. (It means in Sales Items there we can know from which plant we sold the goods, like in EKPO, there is any field like this)
Please let we are defining the report to find out the stock availability for perticular storage location using select Options plant, company code, material no.
How many tables involve her to build this report. and also field names, they come under which table.
Please send me this information ASAP. PLz Plz Plz..........
Regards
Praveen

You can check the fields of these tables via SE11
Purchase Document Date - EKKO-BEDAT
Item Description - EKPO-TXZ01
Net price per item - EKPO-NETPR.
Regards,
Rich Heilman

What are the ideal specs for a DigiBeta master tape when authoring a "widescreen anamorphic" 16:9 SD DVD (original aspect ratio is 14:9)?

I just received the masters for a new SD DVD. I would like to author a "widescreen anamorphic" SD DVD horizontally squeezed widescreen image stored in a standard 4:3 aspect ratio DVD image frame. (On 4:3 displays, mattes should preserve the original aspect ratio. On 16:9 displays the image will fill the screen at the highest possible resolution.)
Below I've listed the specs of the Digi Beta master tapes the producers have sent to me for digitizing. I'd like to know this: What are the ideal specs for a DigiBeta master tape when authoring a widescreen anamorphic SD DVD, using material with an original aspect ratio of 14:9?
I've also listed my guesses below. Please let me know if my guesses are right. If not, please suggest alternatives (and if possible explain why.)
TECHNICAL SPECIFICATIONS OF EXISTING MASTER:
Tape: DigiBeta
Original Aspect Ratio: 1.55 (14:9)
Vid Rate: 29.97 fps
Pixel Aspect: NTSC - CCIR 601
Frame Size: 720 x 480
Anamorphic: Full-Height Anamorphic (16:9 image displayed in letterboxed, non-distored 4:3)
Display Format: 4:3 Letterbox
MY GUESS AT IDEAL TECHNICAL SPECIFICATIONS (for a DigiBeta, that is):
Tape: DigiBeta
Original Aspect Ratio: 1.55 (14:9)
Vid Rate: 29.97 fps
Pixel Aspect: Square
Frame Size: 720 x 540
Anamorphic: YES
Display Format: 16:9 Anamorphic (horizontally squeezed widescreen image)
Please feel free to ask for clarification or further information you need to answer my question.
Thank you so much in advance for your help!
Best, Noetical.
BTW, I can't wait for the day when everything has gone digital and we get digital intermediates instead of tapes to digitize!

Hi Nick...thanks for taking the time to reply to my question.
Nick Holmes wrote:
What you have there is a mess.
NTSC pixels are never square.
NTSC is 720x486, even when it is Anamorphic.
You shouldn't be using an already letterboxed master to make an Anamorphic version. Get the master that was made before the letterboxing stage.
When you make an Anamorphic DVD it should display as 16:9 full screen automatically on widescreen TVs.
The same DVD will automatically letterbox on 4:3 TVs.
Um yeah...duh. That's exactly what I was trying to explain in the preface of my question. I'm sorry if I didn't make it clear...all these things you mention are the reasons I'm putting together a list of the technical specs of the DigiBeta I need so I can have them send that instead of the stupid letterboxed version.
Look, I'm sending this request to some intern at their offices in England, asking for a master with which I can make an Anamorphic DVD. They already sent me this master, which as you and I both agree is an idiotic asset to use for these purposes. As such, I was hoping for advice on a more precise way of requesting the master that I need than asking for "the master that was made before the letterboxing stage." Upon reflection, perhaps I'll just do that. If you or anyone else has a suggestion about something I should add to my request that would improve the odds of them sending the tape I need, please repond. Thank you!
BTW, It's been a long time since anyone has responded to something I've written or said as though I'm an idiot. I remember now that I don't really like it. (Moving along...)

What are the pre requisites for SPLIT VALUATION OF A MATERIALS

Similar Messages

Maybe you are looking for