FI - Structure of DOC_HEAD_TAB - transaction F-28

Hi everybody,
Can anyone tell me what is the 'DOC_HEAD_TAB's' structure?
I'm debbuging the transaction F-28 and I need to use this structure to make a search.
Thanks everybody!
Cesar

Hi Friend,
I thnik the format of the structure DOC_HEAD_TAB is similar to BKPF table.
Regards
Krishnendu

Similar Messages

Message type in BDCMSGCOLL Structure in Call transaction using BDCDATA

Hi,
We are facing issue while capturing message in BDCMSGCOLL structure in Call transaction using bdcdata. The message which are like
Message 'Message Text' Type 'S' Display LIke 'E' .
This message is captured as Success on the Message structure instead of error & user are asking to update it as Error as it is looking like Error message to the end user.
Please provide resolution to the issue.
Regards,
Kapil

Hi Venkat,
I am not doing any upload, i am just doing a replay of the transaction ME21 & in that there are many error message which encounter while creating a PO but when i have check the logic , they are basically a success message which are display like Error so when i have called ME21 transaction using below statement
call transaction ME21 using BDCDATA
into messages bdcmsgcoll.
I am getting the message as success only since the message are of type success but as they are display like E , so user want that in msgcoll structure these messages must be shown as Error.
Regards,
Kapil.

Project Blue Print Structure in Solar01 Transaction

Dear All,
Is it sure that the Project Structure in the Transaction Solar01 will always be remain same , i.e the structure will be as follows:
1.Organizational Units
2.Master Data
3.Business Scenarios
4.Interface Scenarios
And also I want to know that is it possible to change the Node Text , i.e can the names like Organizational Units , Master Data , Business Scenarios , Interface Scenarios differ from one SAP SolMan system to another.
Please post if I am not clear.
If there is some link / URL having the required document regarding it, please post.
Thanking You All.

Hi,
The structure cannot be changed It cannot be renamed either...
What is the need to change the nodes / Change the structure?
Elaborate your requirement.
Feel free to revert back.
-=-Ragu

How is full the "valuated Quantity structure" in CKM3 transaction?

Hello everyone!
I need some help to understand how works the CKM3 transaction, specially the "Valuated Quantity Structure". I need to know where comes those data, in what table can I see the multilevel data that is display on CKM3?. I need the maximun detail level of the Valuated Quantity structure to extract the values of consumption of some products to make the material in the specific plant that I entered as a filter of CKM3.
I attach a image with an example of what level I need to find, I highlight in yellow the level of the information that I need.
Thanks for any help!
Regards,
Rosmar.

Hi,
This is a material ledger component.You can use the datasource: 0CO_PC_ACT_1 for the same and ensure that report is running after the month end close. Let me knowif you need further help.
Regards,
Rajesh

How is full the "Valuated Quantity Structure" of CKM3 transaction?

Hello everyone!
I need some help to understand how works the CKM3 transaction, specially the "Valuated Quantity Structure". I need to know where comes those data, in what table can I see the multilevel data that is display on CKM3?. I need the maximun detail level of the Valuated Quantity structure to extract the values of consumption of some products to make the material in the specific plant that I entered as a filter of CKM3.
I attach a image with an example of what level I need to find, I highlight in yellow the level of the information that I need.
Thanks for any help! Regards,
Rosmar.

Hi Rosmer
1. This OSS explain the tcode 1004597 - CKMLQS: Valuated quantity structure (multilevel)
2. About the tcode:
+ This tcode is some sort of advice.
+The detailed info is in CKM3N.
+ In general, the sum of the componentes is not equal to the cost of the principal material.
3. The info is spread in tables, here just some hints
+ CKML_MGV_BOM_READ: This function gives you the QTYs in the level BOM and Activities. No values here.
+ The values are calculated by the tcode, reading lots of tables and doint lots of calcs. Its a bit difficult to explain. tcode CKMDISPTAB - Technical View of ML Master Data can give you a good advice. In ckmlqs, all the calcs are packed methods, so reuse the code is a bit difficult.
Wish this give you an advice.
Arturo.

How to insert storge location in bestand structure Using MB5B transaction

I have to add storage location in bestand structure . how to add .

try this
For EDI U need SEEBURGER Adapter or Conversion agent by itemfield.
Using Conversion agent convert EDI Into XSD and Import using External definition.
Have look
EDI Conversion
Re: Seeburger Splitter adapter!!
Thanks

Problem to reverse Costs of Structure in transaction CJ46

Hi people. When I do the reversal of the costs of structure, in the transaction CJ46, no reverses all values. Is there any other transaction to reverse the costs of structure?
It is possible to launch a negative value to pay the costs of structure?

Hi, Try this example
DATA:BEGIN OF ITAB OCCURS 10,
      QMNUM LIKE QMEL-QMNUM,
      DESC(72),
     END OF ITAB.
DATA:F_TDOBJECT LIKE THEAD-TDOBJECT,
     F_TDNAME   LIKE THEAD-TDNAME,
     F_TDID     LIKE THEAD-TDID,
     ITAB_LINES LIKE TLINE OCCURS 0 WITH HEADER LINE.
      F_TDID     = 'LTQM'.
      F_TDNAME = T_DET-QMNUM.
      F_TDOBJECT = 'QMMA'.
      CALL FUNCTION 'READ_TEXT'
        EXPORTING
          CLIENT                  = SY-MANDT
          ID                      = F_TDID
          LANGUAGE                = SY-LANGU
          NAME                    = F_TDNAME
          OBJECT                  = F_TDOBJECT
        TABLES
          LINES                   = ITAB_LINES
        EXCEPTIONS
          ID                      = 1
          LANGUAGE                = 2
          NAME                    = 3
          NOT_FOUND               = 4
          OBJECT                  = 5
          REFERENCE_CHECK         = 6
          WRONG_ACCESS_TO_ARCHIVE = 7
          OTHERS                  = 8.
      DESCRIBE TABLE ITAB_LINES LINES SY-TFILL.
      IF SY-TFILL > 0.
        LOOP AT ITAB_LINES.
          ITAB-QMNUM = T_DET-QMNUM.
          ITAB-DESC = ITAB_LINES-TDLINE.
          APPEND ITAB.
          CLEAR ITAB.
        ENDLOOP.
      ENDIF.
reward points if it helps
kaki

How to create a new report from an information structure?

Dear gurus,
My customer wants to have a sales report by product hierachy. I want to create an information structure for product hierachy and create a report from this info structure like a standard report. I dun know which steps to do. Pls tell me how to do. Your help are highly appreciated.
Thank you!
Rgds,
Nghi Do

Hi,
Steps in LIS EXTRACTION:
T.code - :MC18 u2013 create field catalog
1. Characteristic Catalog
Application-01-Sales and Distribution, 02-Purchasing, 03-Inventory Controlling, etc..
Catalog category 1. Characteristic catalog, 2. Key figures catalog 3. Date catalog Select characteristic catalog and enter, click on characteristic select the source table and it will be display the relevant source field and select the source field, copy + close, copy.
Save, similarly create key figures catalog
T.code : MC21 u2013 create infostructure
Example u2013
Inforstructure : S789
Application u2013 01
Choose characteristic select the catalog, select the fields, copy + close Choose key figures catalog select the key figures ,copy + close, save and generate
T.code u2013 MC24 u2013 create updating
Infostructure : S789
Update group : 01- Sales document, delivery, billing document ,enter Select the key figures click on rules for key figures give suggest rules, copy save and generate Click on updating (activate updating) Select the infostructure set periodic split 1. Daily, 2. Week, 3. Month, 4. Posting period Updating u20131)No updating,2)Synchronous updating (V1), 3)As synchronous updating (V2), 4)As synchronous updating (V3),
T.code u2013 LBW0 - Connection of LIS Information structures to SAPBW Information structure : S786 Select the radio button-Setup LIS environment and Execute.
Select the radio button-Generate data source and Execute.
For Delta update:
Select the radio button-Generate updating and Execute Select the radio button -Activate / deactivate and Execute.
T.code u2013 SBIW u2013 Display IMG (implementation guide) Setting for applications specific data source u2013 logistics u2013 Managing transfer information structure u2013 setup of statistical data u2013 applications specific setup of statistical data u2013perform statistical setup u2013 sales.
Choose activity
Setup u2013 Orders, deliveries, billing
Choose the activities enter the infostructure (S789), give name of the run, date of termination, time of termination, No. of tolerated faulty documents. Then execute
T.code u2013 RSA3 u2013 Extractor checker
Give the data source name eg. 2LIS 01S789 and execute, result will get some records Go to BW side replicate data source u2013 Assign infosource u2013 Create infocube u2013 Create update rules u2013 create infopackage and schedule the package with initialize delta process.
For delta update :
In R/3 side
T.code u2013 MC25, set update (V1) or (V2) or (V3)
T.code u2013 LBW0, choose generate updating and execute then choose activate / deactivate and execute
BW side - create infopackage and schedule the package with delta update.
First time if your scheduling the infopackage -in R/3 side T.code :MC25 -Udating set to No update,insted of selecting the update V1,V2,V3.
If your doing the Delta update:in R/3 side T.code :MC25-Updating set to either V1 or V2 or V3. and the to T.code :LBW0 -Select the radio button Active/deactivate and Execute.
and schedule the infopackage with delta update.
Modules for LIS : SD,MM, PP,QM.
Deltas for LIS:
After setting up the LIS environment, 2 transparent tables and 1 extract structure is generated for this particular info structure. Within transaction SE11 you can view the tables u2018SnnnBIW1u2019, u2018SnnnBIW2u2019 and the structure u2018SnnnBIWSu2019 and the InfoStructure itself u201ASnnnu2018
The tables S5nnnBIW1 & SnnnnBIW2 are used to assist the delta update process within BW.
Extract structure u2018SnnnnBIWCu2019 is used as an interface structure between OLTP InfoStructure and BW
The OLTP system has automatically created an entry in the control table u2018TMCBIWu2019. Within transaction u2018SE16u2019 youu2019ll see, that for your particular InfoStructure the field u2018BIW activeu2019 has the value u2018Xu2019 and the field u2018BIW statusu2019 is filled with value u20181u2019 (refers to table SnnnBIW1).
The orgininal LIS update program u201ARMCX#### will be enhanced within the form routines u201Aform Snnnbiw1_update_....u2018 and u201Aform Snnnbiw2_update
With the transaction u2018SE38u2019 youu2019ll see at the end of the program starting at line 870 / 1006, that the program is enhanced within a u2018BIW delta updateu2019 coding
Within the flag u201AActivate/Deactivateu2018 the update process into the delta tables (SnnnBIW1/Sn5nnBIW2) is swichted on/off. In the table u201ATMCBIWu2018 is defined, which table is active for delta update.
Note: The delta updating is client dependent !
Regards,
Ram Pedarla
Edited by: RamPedarla on Apr 1, 2010 10:35 AM
Edited by: RamPedarla on Apr 1, 2010 10:35 AM

What are the parameters in Call transaction method?

Hi ABAPER'S,
Please give me what are the parameters in call transaction method?
Thanks,
Prakash

Processing batch input data with CALL TRANSACTION USING is the faster of the two recommended data transfer methods. In this method, legacy data is processed inline in your data transfer program.
Syntax:
CALL TRANSACTION <tcode>
USING <bdc_tab>
MODE <mode>
UPDATE <update>
<tcode> : Transaction code
<bdc_tab> : Internal table of structure BDCDATA.
<mode> : Display mode:
A
Display all
E
Display errors only
N
No display
<update> : Update mode:
S
Synchronous
A
Asynchronous
L
Local update
A program that uses CALL TRANSACTION USING to process legacy data should execute the following steps:
Prepare a BDCDATA structure for the transaction that you wish to run.
With a CALL TRANSACTION USING statement, call the transaction and prepare the BDCDATA structure. For example:
CALL TRANSACTION 'TFCA' USING BDCDATA
MODE 'A'
UPDATE 'S'.
MESSAGES INTO MESSTAB.
IF SY-SUBRC <> 0.
<Error_handling>.
ENDIF.
The MODE Parameter
You can use the MODE parameter to specify whether data transfer processing should be displayed as it happens. You can choose between three modes:
A Display all. All screens and the data that goes in them appear when you run your program.
N No display. All screens are processed invisibly, regardless of whether there are errors or not. Control returns to your program as soon as transaction processing is finished.
E Display errors only. The transaction goes into display mode as soon as an error in one of the screens is detected. You can then correct the error.
The display modes are the same as those that are available for processing batch input sessions.
The UPDATE Parameter
You use the UPDATE parameter to specify how updates produced by a transaction should be processed. You can select between these modes:
A Asynchronous updating. In this mode, the called transaction does not wait for any updates it produces to be completed. It simply passes the updates to the SAP update service. Asynchronous processing therefore usually results in faster execution of your data transfer program.
Asynchronous processing is NOT recommended for processing any larger amount of data. This is because the called transaction receives no completion message from the update module in asynchronous updating. The calling data transfer program, in turn, cannot determine whether a called transaction ended with a successful update of the database or not.
If you use asynchronous updating, then you will need to use the update management facility (Transaction SM12) to check whether updates have been terminated abnormally during session processing. Error analysis and recovery is less convenient than with synchronous updating.
S Synchronous updating. In this mode, the called transaction waits for any updates that it produces to be completed. Execution is slower than with asynchronous updating because called transactions wait for updating to be completed. However, the called transaction is able to return any update error message that occurs to your program. It is much easier for you to analyze and recover from errors.
L Local updating. If you update data locally, the update of the database will not be processed in a separate process, but in the process of the calling program. (See the ABAP keyword documentation on SET UPDATE TASK LOCAL for more information.)
The MESSAGES Parameter
The MESSAGES specification indicates that all system messages issued during a CALL TRANSACTION USING are written into the internal table <MESSTAB> . The internal table must have the structure BDCMSGCOLL .
You can record the messages issued by Transaction TFCA in table MESSTAB with the following coding:
(This example uses a flight connection that does not exist to trigger an error in the transaction.)
DATA: BEGIN OF BDCDATA OCCURS 100.
INCLUDE STRUCTURE BDCDATA.
DATA: END OF BDCDATA.
DATA: BEGIN OF MESSTAB OCCURS 10.
INCLUDE STRUCTURE BDCMSGCOLL.
DATA: END OF MESSTAB.
BDCDATA-PROGRAM = 'SAPMTFCA'.
BDCDATA-DYNPRO = '0100'.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
CLEAR BDCDATA.
BDCDATA-FNAM = 'SFLIGHT-CARRID'.
BDCDATA-FVAL = 'XX'.
APPEND BDCDATA.
BDCDATA-FNAM = 'SFLIGHT-CONNID'.
BDCDATA-FVAL = '0400'.
APPEND BDCDATA.
CALL TRANSACTION 'TFCA' USING BDCDATA MODE 'N'
MESSAGES INTO MESSTAB.
LOOP AT MESSTAB.
WRITE: / MESSTAB-TCODE,
MESSTAB-DYNAME,
MESSTAB-DYNUMB,
MESSTAB-MSGTYP,
MESSTAB-MSGSPRA,
MESSTAB-MSGID,
MESSTAB-MSGNR.
ENDLOOP.
The following figures show the return codes from CALL TRANSACTION USING and the system fields that contain message information from the called transaction. As the return code chart shows, return codes above 1000 are reserved for data transfer. If you use the MESSAGES INTO <table> option, then you do not need to query the system fields shown below; their contents are automatically written into the message table. You can loop over the message table to write out any messages that were entered into it.
Return codes:
Value
Explanation
0
Successful
<=1000
Error in dialog program
> 1000
Batch input error
System fields:
Name:
Explanation:
SY-MSGID
Message-ID
SY-MSGTY
Message type (E,I,W,S,A,X)
SY-MSGNO
Message number
SY-MSGV1
Message variable 1
SY-MSGV2
Message variable 2
SY-MSGV3
Message variable 3
SY-MSGV4
Message variable 4
Error Analysis and Restart Capability
Unlike batch input methods using sessions, CALL TRANSACTION USING processing does not provide any special handling for incorrect transactions. There is no restart capability for transactions that contain errors or produce update failures.
You can handle incorrect transactions by using update mode S (synchronous updating) and checking the return code from CALL TRANSACTION USING. If the return code is anything other than 0, then you should do the following:
write out or save the message table
use the BDCDATA table that you generated for the CALL TRANSACTION USING to generate a batch input session for the faulty transaction. You can then analyze the faulty transaction and correct the error using the tools provided in the batch input management facility.

In Scope missing in Transaction tab

Hi All,
My company has recently started to work with Solution manager.
We have created a template project in solution manager that contains all our processes.
I'm now tasked by testing the testing functionality of solution manager.
By reading and doing some initial testing I noticed that we do not have the "In Scope" column in the transactions tab.
Is this only available in implementation projects or did we configure something wrong?
regards,
Peter

Hi Peter,
scoping is generally not possible in Template projects, neither in structure nor on transaction tab.
Regards
Andreas

When we have to go for session method, when we have to go for call transact

when we have to go for session method, when we have to go for call transaction method if i have a 3000 records in flat file. which is better? why

Data Transfer
During the process of data transfer, data is transferred into the SAP R/3 System. This transfer is from an external system to SAP R/3 system. Whenever you transfer data from an external system into an R/3 System, you can use data transfer because it is installed and regularly transfers data from an external system into an R/3 System.
As discussed, with the help of BDC, you can transfer the required data from a non-SAP system to an SAP system. For this kind of data transfer you are required to write an ABAP program. This ABAP program would help to export the concerned data to a sequential dataset file. The data in this file has to be stored. This should be stored in a format, which is acceptable to SAP batch input program. But, to transfer data from a SAP system to another SAP system, you can take the aid of RFC or CPI-C.
SAP application supports the data transfer of numerous SAP business objects. The said data transfer program specifies the data format definition, which is necessary to import the data into the R/3 System. There are three methods available for transferring data:
Direct Input:
In this method the SAP function modules execute the consistency checks. However, there are other means of checking with the help of screens. The Direct Input Method has considerable performance advantages.
Call Transaction:
In this method you can check the data consistency with the help of screen logic.
Batch Input Session:
In this method data consistency is checked with the help of screen logic.
Direct Input Method
Among the methods of data transfer through BDC, direct input method is the one that is used, especially in case of transferring large amount of data. In order to enhance the batch input procedure, the system offers you with the direct input technique.
There is a distinction between the batch input technique and this technique. Unlike batch input technique, this technique does not create sessions. Instead, it stores the data directly. Moreover, it does not process screens. The data has to be entered directly into the corresponding database tables. The system calls a number of function modules which execute necessary checks, if any required. In the case of errors, the direct input technique has a facility to restart the entire mechanism. However, if you want to restart the entire mechanism in case you faced an error, then direct input programs must be executed in the background only. One has to use program RBMVSHOW or Transaction BMV0 to maintain and start these programs.
Call Transaction Method
Call Transaction method is another method used for Data Transfer. In this type of method your program will use the ABAP statement CALL TRANSACTION USING in order to run a SAP transaction. In this type external data need not be deposited in a session for being processed later on. Instead, the entire batch input process takes place inline in your program.
Here, the data transfer program must convert the data that has to be transferred into the SAP system. This is as per requirement by the SAP data structure or the transaction which is using it. It is to be remembered that a conversion of the data types may be necessary at different times during the process.
Suppose there is a data type mismatch then you have to convert the data types to type C. In this regard the data transfer program should be capable of exporting the data in SAP format to the sequential file. At the time of uploading the data into the SAP system, the BDC program reads the data from the abovementioned sequential file.
Batch Input Session Method
This is the third method for data transfer. If you use the batch input method to transfer data, then you should remember that an ABAP program has to read the external data which is to be entered in the R/3 System. Subsequently, it stores the concerned data a "batch input session." The batch Input session records the actions which are required in the process of transferring data into the system. This can be done by using normal SAP transactions.
As soon as the program generates the said session, you will be able to run the session in order to execute the SAP transactions in it. Moreover, you can start the session, and at the same time, can monitor a session with the help of batch input management function. For this you have to choose:
System à Services à Batch input. Moreover, you can have the session run in the background processing.
Writing a Data Transfer Program
If you want to write a data transfer program, you have to follow the steps mentioned below.
Firstly, you will analyze the structure of the existing data. Subsequently, your job is to specify the conversions, which are essential to fill the SAP data structures.
Secondly, you have to generate the SAP data structure. In case the program is written in ABAP, you will require only the required tables in the concerned program with the help of TABLES statement.
Thirdly, you will have to initialize the SAP data structure.
Fourthly, fill the structure with data, performing any conversions and error checking that are required.
Finally, you will write the sequential file. In the SAP system this sequential file is typically required for making the data available to the batch input program.
Batch Input Method
Batch input method is a type of data transfer method. It is used for bulk data transfer; it is one of the primary ways by which data can transferred into the R/3 System. This method is not for near real-time data transfers.
There are various typical uses of batch input. One of the ways includes the one-time import of data. This import of data is from a legacy system into a newly installed R/3 System. In addition to it, another typical use is for periodic (i.e. hourly, daily..., and so on) transfers of data. These transfers are from external systems or legacy systems which are still in use into R/3 system where all enterprise data is consolidated.
The R/3 applications deliver different programs for batch input, which are ready to be used. However, in some cases a customer has to write his or her own batch input program. This is required in order to convert the concerned data from a legacy System or from a proprietary format into an R/3 data format.
The process flows for a batch input are discussed below.
Data Transfer Decision-Making: It is with a decision to transfer data from an external source into R/3 that the process of batch input begins. It is probable that the external source may be a legacy system that is being replaced. A one-time bulk data transfer is foreseen in this regard. Alternatively, the external source may be an external system that is to remain in use. In this case, a regularly recurring bulk data transfer is foreseen.
Setting up Batch-Input for Data Transfers: If R/3 standard one-time or regular data transfers are required, then by means of customizing settings in the R/3 Customizing System in SAP ASAP set up will occur. You must set up custom batch input procedures by hand, which means the system administrator must schedule the data conversion program that creates the batch input session. The system administrator and the batch input programmer must determine the following: how frequently data is made available from the external system, how frequently the conversion program should run, and whether the conversion program runs in R/3 (ABAP program) or in a host system (external program).
Processing Batch Input Sessions: When a batch input session is processed, then the actual transfer of data into R/3 takes place. Little attention is required in processing of batch input sessions by the system administrator. Usually, the starting of batch input sessions is automated by the system administrator. If necessary, the administrators can also start batch input session explicitly from transaction SM35.
Checking Batch Input Sessions: For a system administrator the routine activity is to check daily or more frequently in transaction SM35 whether all batch input sessions have been completed successfully. It is the schedule for running batch input sessions on which the schedule for checking sessions depends upon. For doing this check the R/3 System provides easy-to-use batch input management tools.
Analyzing Errors: It is the duty of the system administrator to analyze the problem if one or more transactions in a session end in errors. Usually, the assistance of the affected data entry specialist or department for this analysis will be needed by the system administrator. In the situation where the problem was caused by incorrect data conversion or incorrect generation of the batch input session then the programmer who wrote the data conversion program may also need to be involved.
Error Handling in Batch Input Method
It is found that most problems usually fall into one of the following two categories discussed below.
In this case either required data is missing from the batch-input session or invalid data has been included in the session. Errors in the data conversion program or the presence of unexpected types of data or incorrect data in the legacy database are the possible external causes of this type of problem. Within R/3, the causes for this type of problem include incorrect or incomplete customizing in an application. For example, a legacy data type may not have been foreseen in the check table entries made in application customizing.
This case mainly includes technical/programming problems. The data is entered by a batch input session by running R/3 transactions non-interactively. Therefore, a typical technical or programming problem is the incorrect identification of one of the data fields in a transaction. Thus, the conversion program may not fill a required data field or may have provided invalid values.
Conclusion
I have gone through the details of batch data communication and various methods used to transfer data. One can make use of BDC to transfer data from a SAP to SAP system. In addition, it can transfer data from a non SAP system to SAP system too. I have discussed the various methods of BDC and the error handling in the respective methods.
Thanks,
Shankar

ABAP Proxy : Modification in Structure 2

Hi,
I try to modify a structure but i can not do that, because is "Proxy Structure (generated)", I excute the transaction SPROXY in order to modify this structure but i don't know how to find it
Pls help , how to find the structure in this transaction, and how modify.
Omar.

Hi,
You have to re-create the web service. There are lots of ways to generate ABAP web service. Ask the person who is responsible for (or the person who created) the web service for instructions.
For example, if the web service is created by SAP Duet Enterprise, I will not use any tools other than SAP Duet Enterprise to change it. If the web service is created from a RFC, I will change the RFC and re-generate the web service.

Creating a Web Service Proxy for a transaction with Microsoft Visual Studio

Hi experts out there,
I have created a simple transaction which I'd like to call as a webservice. Getting the WSDL from an authenticated browser (from which I started the xMII Workbench) works fine. But when I try to create a Web Reference within my Visual Studio project I only get the following output:
"XacuteWS" Description
Methods
Xacute ( LoginName As string , LoginPassword As string , InputParams As InputParams ) As Rowset
I think this is because my visual studio is not authenticated with the xMII server. So is there any way to achieve this? I have to find a way to generate a .NET proxy for out xMII web services because otherwise it would be too complicated to use the web services from within our .NET applications.
Thanks in advance for any hint on this topic!
Achim

Two comments:
1) The generated proxy looks correct. If you explore the generated code for the InputParams object and the Rowset object, they should represent the incoming and outgoing data structures for your transaction. If not, and if you are returning an XML property type from the transaction, be sure that you have used the "Assign Reference Document" technique to tell MII what the structure of your outgoing document is (there are a few other discussion threads on that topic).
2) Personally, I find it much easier to consume MII services from .NET code using a URL-based technique instead of a SOAP based technique. Invoke the "Runner" servlet (see the documentation) and you'll get an XML document back, that will always be in the MII Rowsets/Rowset/Row format. Also, it is "self describing" because it includes Column metadata information. It is very trivial to load this into a .NET XmlDocument object and parse/process it. In fact, doing a similar approach, I've been able to make MII services appear as ADO.NET tables/stored procedures to .NET code.
Rick

Problem with Self defined info structure.

Hi All,
We have Create some Self define Info structure Like ;--
S061 Location and Planning               --->S501
S062 object class and manufacturer --->S502
S063 Danage analysis                        --->S503
S065 Object Statistics                         --->S504
But probleme is when we excute S501 self defined info structure heading comes as
Standard Analysis for Info Sstructure S501: Selection where as in Standard it is coming as Location Analysis: Selection
Any one can tell how can i solve this probleme.
Thanks
Vinit

steps to create own infostructure by copying standard infostructure.
steps.... 1) First Create your own info structure using menu path SPRO> Logistics general > LIS > Logistics data warehouse > Data basis > information structure > maintain self defined ino structure Here create a New stucture called S901 (Follow Custom defined structure naming conventions) for application 07, by copying S115 .
Once inside this Choose the Charateristic button below and CHOOSE SELECTION LIST.
This will popup a list of fields that can be added to the structure for analysis per field catalogue.
Navigate to the notification Object field catalog to select the Order number.
Select other field as appropriate from other field catalog and copy them.Then select or de-select the "Key figures" thats relevant for your needs Check ,generate and activate the same structure and save.
2) Create Update rules for updating this info structure by copying the rules of S115.
SPRO> Logistics general > LIS > Logistics data warehouse > Data basis >Updating > Specific definition using update Rules > Maintain update rules.
Enter the newly created Structure name and choose teh Update group 26 (use drop down) and enter the S115 and 26 as teh group and rules to copy from.
Delete the rules thats not relevant for your needs and then check, and Choose "generate: and then activate the "UPDATING" and save.
3) Activate the Update type for the new structure. SPRO> Logistics general > LIS > Logistics data warehouse > Data basis >Updating > Update Control > Activate Update.
Choose PM and double click on the new structure that you had just created and chosoe Period and Type of updating (2: Similar to other standard info structures). and save.
This should start updating New orders that you are creating from Now on.
However if you would like to pre-populate existing data in this structure for analysis, then you would have to run through the generation program in background for this specific structure.
SPRO> Logistics general > LIS > Logistics data warehouse > Data basis >tools > setup of statistical data >Application specific setup of statistical data > perform setup - PM.
Here make sure to do the PMIS statistical setup (This might be redundant, if you havent changed any value category that updates PMCO table) and Set Up: Plant Maintenance IS(Make sure to choose your specific structure).
You should be able to check the table entries to confirm that the program has updated the table (Name of the info structure).
The defaulted version could be different from the standard version (000).You could copy the data from one verion to another version using the first step in this block.
Once the genration is complete you should be ready to use this structure using MCIS transaction (PMIS > Standard analysis > User defined analysis).
This will list out all the user defined structures and you can pick and execute the one that you had just created.
Regards
Dhiren
Edited by: Dhiren Kumar Sahoo on Feb 2, 2010 3:55 PM

How to add button on application tool bar of standard transaction

Hi All,
Can any one let me know how to ADD the button in on application tool bar of standard transaction by using SHD0 transaction or any other solution.While adding the button I don't want do any code modification.
Thanks,
Vijay

HI
SHD0 is used to create and maintain Screen and Transaction Variants..
to know more about Screen and trransaction variants click on this link
http://help.sap.com/saphelp_47x200/helpdata/en/67/232037ebf1cc09e10000009b38f889/content.htm
we can create Transaction Variants Using SHD0 Transaction.
Transaction Variants and Screen Variants
Transaction variants can simplify transaction runs as they allow you to:
Preassign values to fields
Hide and change the 'ready for input' status of fields
Hide and change table control column attributes
Hide menu functions
Hide entire screens
In particular, hiding fields in connection with screen compression, and hiding screens, can result in greater clarity and simplicity.
Transaction variants are made up of a sequence of screen variants. The field values and field attributes for the individual screens found in transaction variants are stored in screen variants. Each of these variants is assigned to a specific transaction, can, however, also contain values for screens in other transactions if this is required by transaction flow. The transaction that the variant is assigned to serves as initial transaction when the variant is called.
There are both client-specific and cross-client transaction variants. All screen variants are cross-client, but may be assigned to a client-specific transaction variant.
A namespace exists for cross-client transaction variants and screen variants and both are automatically attached to the Transport Organizer. Client-specific transaction variants must be transported manually.
In principle, transaction and screen variants can be created for all dialog and reporting transactions. There are, however, certain Restrictions that apply to certain transactions, depending on their internal structure.
No transaction variants are possible with transactions already containing preset parameters (parameter transactions and variant transactions).

FI - Structure of DOC_HEAD_TAB - transaction F-28

Similar Messages

Maybe you are looking for