Set Types not in IDOC

Dear Experts,
Currently I am working on an interface between CRM 6.0 and XI to deliver product specific information, including customer fields.
I am using the BDOC type PRODUCT_MAT.
The customer fields have been implemented through set types in transaction comm_attrset. For each set type an API append was created successfully through function u201CSet types/attributesu201D > u201CTransportu201D > u201CSet Typeu201D.
The set types are available in the API structure of the BDOC PRODUCT_MAT (structure COMT_PROD_MATERIAL_BDOC_TAB). But the set types are not available in the generated IDOC (I use the function module CRMXIF_PRODUCT_MATERIAL_SAVE to generate the IDOC...).
Has anybody of you an idea why the set types are not in the IDOC / how to get the set types into the IDOC?
Thanks in advance,
Alex

Dear Vamsi,
Thanku2019s for your reply. I checked the module CRMXIF_PRODUCT_MATERIAL_SAVE, but it has no output structure named CUSTOMER_SET_DATA which could hold the set types.
Any other hints?
At the moment I am wondering what might be the general process to add set types to IDOCs? Are set types generally also added to IDOCs as soon as they are generated and added to BDOCS, or is there a different mechanism like generating the IDOC structure from the BDOC structure?
Thanks for any answers in advance!
Regards,
Alex

Similar Messages

Load customized set type using LSMW+ IDOC (XIF)

Hi experts,
now i could load most product field using LSMW+ IDOC (XIF), but when i load customized set type, it gives error " User-defined set type ZTest does not exist in BDOC structure ". After some study i know i must to enhance BDOC type ? but i am not very familiar with BDOC, andy idea ? ths
also could anyone provide some function module to load product ? ths again
Edited by: Gang LI on Apr 23, 2009 11:57 AM

Hi,
You will have to Re-Generate Your BDoc Structuring due to your Carried out Changes,
Use TCode:SMW_BDM
For Creation of the BDoc and Check.
Hope it answers your Queries..
Thanks and Regards,
RK.

STARTUP paramter set type not available..?

Hi guys,
Regarding the SAP help
"Defining Parameter Sets"
http://help.sap.com/saphelp_nw04s/helpdata/en/f4/d50f412d72f323e10000000a155106/content.htm
there should be Parameter Set type "STARTUP", however I cannot find it in the list of
the types in the WebAdministrator I am using.. The middleware MI is of versions: NWMADMIN 12.1, NWMCLIENT 12.4, NWMDRIVERS 12.0 и NWMDRIVERS 12.0.
Do you know in which version it is accessible.. or maybe it is a matter of additional settings..?
Thanks!
Best Regards,
Lalo Ivanov

No dial tone mean the system is not ready for dialing. But it's hard to guess why without detailed information. Turn on debugging, catch syslog and debug messages, catch SIP control packets as well. It will help with the further analysis.
Debug and syslog Messages from SPA1x2 and SPA232D ATA (Analog Telephone Adapters)
Installing and Using Wireshark for Capturing Network Traffic

Pairing of EDI ASNI X.12 Transactions set with suitalbe SAP IDoc types

Hello,
I am looking to pair the following EDI ASNI X.12 Transactions set with suitalbe SAP IDoc types, for our EDI Integration.
Can some one help me to identify which suitable IDoc type, should I use? Your help is greatly appreciated.
142
824
830
846
853
861
862
864
866
I am not sure, I am seeking the help in the righr forum -:)
Thanks in advance.
Namadev

Hi namadev
Please you can check this link.
http://www.erpgenie.com/sap/sapedi/ansi.htm#Mapping_x12_to_SAP
thanks.

For the new delivery type created the Idoc is not getting triggered

Hi All,
I am facing the following problem:
For every outbound delivery getting created we have an Idoc which creates the file(sending the outbound delivery details), this file is sent to a system where the picking & packing of the goods happen. This process seems to be working fine for all the existing delivery types, but now we created a new delivery type for which the Idoc is not getting triggered.
Would like to understand what setting are we missing because of which the Idoc is not getting created for the new delivery type.
The Idoc being used is: DESADV01
Message type :DESADV
Thanks,
Geeta

I believe your existing idocs are created through a output type on the delivery ? if yes, probably you need to configure an existing output type / create a new output type for your new delivery type...

Set type is not getting filled

Hi ,
I have created a set type ZTLS_ORG, which is organisation dependent. This set type has fields from table MVKE. I am filling up the fields of this set type in an enhacement of Badi Definition Customer_product2. But the values are not getting populated, when I am checking it in product master through commpr01. Kindly suggest.
Regards
Shweta

Hello Shweta,
You mean to say that attributes of your settype is nothing but fields from table MVKE?
Have you generated the settype before using it in your program?
Best Regards,
Shanthala Kudva.

JDBC-ODBC Bridge to SPSS data files - Result Set Type is not supported

Hello,
As mentioned in the subject I am trying to read SPSS data files using the SPSS 32-Bit data driver, ODBC and the JDBC-ODBC Bridge.
Using this SPSS Driver I manged to read the data directly into an MS-SQL Server using:
SELECT [...] FROM
OPENROWSET(''MSDASQL.1'',''DRIVER={SPSS 32-BIT Data Driver (*.sav)};DBQ=' SomePathWhereTheFilesAre';SERVER=NotTheServer'', ''SELECT 'SomeSPSSColumn' FROM "'SomeSPSSFileNameWithoutExt'"'') AS a
This works fine!
Using Access and an ODBC System DNS works for IMPORTING but NOT for LINKING.
It is even possible to read the data using the very slow SPSS API.
However, when it comes to JDBC-ODBC the below code does only work in part. The driver is loaded successfully, but when it comes to transferring data into the resultset object the error
SQLState: null
Result Set Type is not supported
Vendor: 0
occurs.
The official answer from SPSS is to use .Net or to use their implementation with Python in their new version 14.0. But this is obviously not an option when you want to use only Java.
Does anybody have experience with SPSS and JDBC-ODBC??? I have tried the possible ResultSet Types, which I took from:
http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/ad/rjvdsprp.htm
and none of them worked.
Thank you in advance for your ideas and input & stay happy!
Here the code without all the rest of the class arround it:
// Module: SimpleSelect.java
// Description: Test program for ODBC API interface. This java application
// will connect to a JDBC driver, issue a select statement
// and display all result columns and rows
// Product: JDBC to ODBC Bridge
// Author: Karl Moss
// Date: February, 1996
// Copyright: 1990-1996 INTERSOLV, Inc.
// This software contains confidential and proprietary
// information of INTERSOLV, Inc.
public static void main1() {
String url   = "jdbc:odbc:SomeSystemDNS";
String query = "SELECT SomeSPSSColumn FROM 'SomeSPSSFileName'";
try {
    // Load the jdbc-odbc bridge driver
    Class.forName ("sun.jdbc.odbc.JdbcOdbcDriver");
    DriverManager.setLogStream(System.out);
    // Attempt to connect to a driver. Each one
    // of the registered drivers will be loaded until
    // one is found that can process this URL
    Connection con = DriverManager.getConnection (url);
    // If we were unable to connect, an exception
    // would have been thrown. So, if we get here,
    // we are successfully connected to the URL
    // Check for, and display and warnings generated
    // by the connect.
    checkForWarning (con.getWarnings ());
    // Get the DatabaseMetaData object and display
    // some information about the connection
    DatabaseMetaData dma = con.getMetaData ();
    System.out.println("\nConnected to " + dma.getURL());
    System.out.println("Driver       " +
      dma.getDriverName());
    System.out.println("Version      " +
      dma.getDriverVersion());
    System.out.println("");
    // Create a Statement object so we can submit
    // SQL statements to the driver
    Statement stmt = con.createStatement(ResultSet.TYPE_FORWARD_ONLY ,ResultSet.CONCUR_READ_ONLY);
    // Submit a query, creating a ResultSet object
    ResultSet rs = stmt.executeQuery (query);
    // Display all columns and rows from the result set
    dispResultSet (rs);
    // Close the result set
    rs.close();
    // Close the statement
    stmt.close();
    // Close the connection
    con.close();
}

Thank you for your reply StuDerby!
Actually the above script was before, as you suggested, leaving the ResultSetTeype default. This did not work...
I am getting gray hair with SPSS - in terms of connectivity and "integratebility" none of their solutions offered is sufficient from my point of view.
Variable definitions can only be read by the slow API, data can only be read by Python or Microsoft Products... and if you want to combine both you are in big trouble. I can only assume that this is a company strategy to sell their Dimensions Platform to companies versus having companies developping their applications according to business needs.
Thanks again for any furthur suggestions and I hope, that some SPSS Developper will see this post!
Cheers!!

The operation is not allowed for result set type FORWARD_ONLY

Hi,
I am trying to use scroll insensitive resultset in following manner-
Statement stmt = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_READ_ONLY);
ResultSet rs = stmt.executeQuery("some sql here");
rs.last();
but the rs.last() throws this exception-
com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB: The operation is not allowed for result set type FORWARD_ONLY.
     at com.sap.dbtech.jdbc.ResultSetSapDB.assertNotForwardOnly(ResultSetSapDB.java:2725)
     at com.sap.dbtech.jdbc.ResultSetSapDB.last(ResultSetSapDB.java:557)
Database version: Kernel    7.5.0    Build 019-121-082-363
Driver Version: MaxDB JDBC Driver, MySQL MaxDB, 7.6.0    Build 030-000-005-567
This used to work with 7.5 version driver. Why this is failing with 7.6 driver, any clues?
Thanks,
Vinod

Hi Vinod,
due to performance improvement when using forward only cursor we changed the default for the resultset type from TYPE_SCROLL_SENSITIVE to TYPE_FORWARD_ONLY starting with JDBC driver version 7.6. So I guess the exception comes from a statement where you didn't set the resultset type while creating it. Please check if all of the statements that you want to be scrollable have set the correct resultset type.
Regards,
Marco

Set type COMM_PR_UNIT is not allowed for product type

Hello all, I am working in SRM 7.0 and when I try to replicate service master (DNL_CUST_SRVMAS) I have this error:
Set type COMM_PR_UNIT is not allowed for product type
What can I do? I think that is an ABAP problem
Thanks in advance
Rosa Rodríguez

Rosa,
This note is something different and nothing to do with the issue. Can you share how did you resolve the DNL_CUST_SRVMAS issue? We are also getting same error.
Thanks,
Jagadish

Default customer type not set by default

hello,
we are having and issue with the "customer type" not being set by default.
When a new customer is created (when they make a purchase) I would like them to be set as “Retail Customer” as their customer type .
I have set the default customer type to be “retail customer” however this is not applied to the customer.
has anyone else struck this problem? is there a fix for this?
thanks in advance for the help.

This is as expected/normal behaviour.
If you create a column in a list that already has items it will not automatically set that column to the default option. Instead any pre-existing items will have a blank value until/unless the item is next edited. At that point you can chose a value but
it still will not populate with the default value.
That is deliberate as it may be entirely valid to have blank entries and so overwriting those would be much worse than leaving entries blank.

IDOC - process code with error "Application Object Type not planned'

Hi all,
I am doing an inbound idoc.... in TCODE we42, i trying to put function module which i created, attached to the process code.
However, when i put my function module ZIDOC_INBOUND to the process code... it comes out error, 'Application Object Type not planned.'
Why is this so?
Please advice...
Thanks and regards...
William Wilstroth

HI all,
I had solved this problem. I should have gone to we57 to tie the function module.
thanks.
William Wilstroth

Document type not defined in lsmw idoc method

hello iam posting Open AR Line Items for contract account using message type
CTRACDOCUMENT_CREATE using lsmw idoc method .iam getting error as Document type not defined but actually when iam creating document manually item is created with out any error that means it is defined and my functional consultant is also saying he defined document type.can some body explain me what is the problem.
Regards
priya

Check OMW9, here document type is defined for the transaction MIRO..
Go to OMW9, click in the Document Type.
Then double click on MIRO.
Also check the sap notes which is referred in the similar thread Document type not defined f5814

How to main multiple attributes for set type R E W ARD_PRO_LOY using IDOC?

Hi,
I'm now trying to add the set type and attributes to my products existing in the CRM system. I decided to use LSMW and IDOC CRMXIF_PRODUCT_MATERIAL_SAVE to maintain the set type and attributes.
I successfully maintained the categories for the products and also assigned the set type. Now I need to add the attributes for this set type, where there are 3:
LMPRODUCT_TYPE
LOYPRODUCT_UNIT
LMPRODUCT_VALUE
But because in the IDOC structure only one attribute can be maintained at one time, how can I input all those 3 attributes together? Thanks a lot.

I tried to insert one data field first then update it by the second attributes, but then the system assigned two separated lines of data to my set type....

Set type COMM_PR_UNIT does not exist

Hi All
How do i make set types available for assignment to categories if they are not available but are there in comm_settype. Getting errors as follows: Set type COMM_PR_UNIT does not exist.
Please assist
Regards,
Patrick
Edited by: Patrick Chidarara on Jul 22, 2008 10:14 AM

Hi Patrick,
Please see OSS note Note 966072 - Download of material fails - set type COMM_PR_UNIT
Regards,Nishant

IDOC - Application object type not planned

Hi all,
I am doing an inbound idoc.... in TCODE we42, i trying to put function module which i created, attached to the process code.
However, when i put my function module ZIDOC_INBOUND to the process code... it comes out error, 'Application Object Type not planned.'
Why is this so?
Please advice...
Thanks and regards...
William Wilstroth

Sorry... i think this should be in Data Transfer section

Set Types not in IDOC

Similar Messages

Maybe you are looking for