Idoc Type for Organization Data

Hi,
I need to send Organization Data details through Idoc, those are
        Company Code
        Controlling Area
        Business Area.
Can anybody give IDOC type for above requirement. Thanks inadvance.
Regards,
Venkat

Dear Mohan,
Thanks for your valuable time and information.
That Idoc type u given is for Cost Centre master data. We found this through T.code BD16.
Can you give info Reg. Company Code, Business Area etc.
Regards,
Venkat

Similar Messages

What are the two different rules for organizational data determination

What are the two different rules for organizational data determination???

Hi
1) Rule type Responsibilities
want to determine organizational data for individual responsibilities
have not created an organizational model but want to create one
have a lot of organizational units and must only assign a few attributes
2) Rule type Organizational Model
You would use rule resolution using organizational model if you
have created an organizational model or have distributed a plan to SAP CRM and also want to use this for determining organizational data
assign a lot of attributes to the organizational units and these are to be evaluated
Regards
Manohar

Corresponding IDOC types for 816 and 824 of X12 tranasction

hi
can anyone tell me corresponding IDOC types for the fallowing X12 tranasction(EDI).
816 Organizational relationships
824 Application Advice
regards
mallikarjun

Hi Malikarjun and Ryan
Please take a look at the following links:
http://www.sapgenie.com/sapedi/ansi.htm
http://www.sapgenie.com/sapedi/mapping.htm
Hope this will help.
Regards,
Ferry Lianto

Idoc type for personnel area

Hello Everyone,
Could someone please let me know Idoc type for sending personnel area details.
We want to send Idoc whenever a new personnel area is created / changed in SPRO.
Best Regards,
Priyanka Gupta.

Hello Priyanka,
Use the standard idoc Message Type HRMD_A for master data and then you can included the following code in FILTER_VALUES_SET method of the BADI implementation by T code BD64
CHECK OTYPE = 'P '.
*SELECT * FROM PA0001*
INTO PA0001 WHERE PERNR = OBJID
AND BEGDA <= SY-DATUM
AND ENDDA >= SY-DATUM.
record is valid today, no authorization check*
EXIT.
ENDSELECT.
IF SY-SUBRC = 0.
FILTER1 = PA0001-BUKRS. ELSE.
CLEAR FILTER1.
ENDIF.
Note: the record you are testing for has your desired company code PGPB.
regards

Idoc Type for Vehicle Master

Hi Friends,
Can any body tell me the Idoc type for
1. Vehicle Master 2. Transport unit and their respective transaction code to send data.
Points would be awarded for useful answers.
With Regards
Vasu

Hi,
Please maintain distribution model (BD64) and partner profile (WE20), RFC connection (SM59) for message type DEBMAS (customer), DEBMAS (vendor) and MATMAS (material master).
Once the above configuration done, then you can use the following transactions to send the IDocs.
1. BD12 - Send Customer IDocs (Sender -> Receiver) or
     BD13 - Get Customer IDocs (Receiver -> Sender)
2. BD14 - Send Vendor IDocs (Sender -> Receiver) or
     BD15 - Get Vendor IDocs (Receiver -> Sender)
3. BD10 - Send Material IDocs (Sender -> Receiver) or
     BD11 - Get Material IDocs (Receiver -> Sender)
Regards,
Ferry Lianto

IDOC type for interface between SAP ECC and SAP F&R

Hi Experts,
I need SAP standatd IDOC type for interfacing between SAP ECC and SAP F&R [SAP Forecasting and Replenishment] using message type u201CFRE_LOC_SITEu201D.
Please help me in finding the idoc type?
Regards,
Krishan

Hi Denish,
You have 2 ways of loading data from R/3 to APO.
1. R/3 to BW cube to APO-BW cube to APO planning area
or
2. R/3 to APO-BW cube to APO planning area
BW can be a enterprise BW system ( independent) or you can use the BW inbuilt in APO also referred to as APO-BW.
The only difference between the 2 BW systems is APO-BW can not take the load of reporting where as the enterprise BW can.
Unless your company policy requires the enterprie BW system, I suggest using 2nd way.
You can load the data from R/3 to APO-BW cube using extractors either generic or standard depending on your data. You need to have a RFC connection setup between APO-BW and R/3. ( This is not CIF).
When you load the data into the APO-BW cube, you just have to load the data from the cube to APO planning area using the transaction /sapapo/tscube.
Refer to [DP Data Mart|http://help.sap.com/saphelp_scm50/helpdata/en/13/5ada58309111d398250000e8a49608/frameset.htm] for more information about the data transfer between APO-BW and APO.

Idoc Type for Billing

Hi
I need some help in knowing which Idoc type is to be used for sending invoice to external system and what is the method of finding the Idoc type for this purpose
Manu Seth

Hi,
Use transaction code WE60.
In the basic type field enter INV* and click on the drop down button.
The system will display list of IDOCS starting with INV.
The IDOC types used for Invoice/billing documents are INVOIC01/INVOICO2 (Incoming/Outgoing).
You can get the documentation in the same transaction code c-header and HTML format buttons.
You can also check the link [EDI -IDOC interface|http://help.sap.com/printdocu/core/print46c/en/data/pdf/SDEDI/SDEDI.pdf] for details.
Regards,

Idoc Serialization for Transactional data

Hi All,
1. Please let me know if you have done IDOC serialization for Transactional data.
If so please let me know the steps.
2. How do we use serialiazation using object types. If you have done this please let me know the steps for this too.
Thanks for your help.
Srikanth.

Hi Srikanth,
Follow the steps below to set up serialization using object types:
1.       In the SAP menu choose ® IDoc Interface/ALE ® Development ® BAPI ® Serialization ® Serialization Using Business Objects ® Determine Supported Business Objects (transaction BD105). Enter all the business object types relevant for serialization.
2.       In the SAP menu choose ® IDoc Interface/ALE ® Development ® BAPI ® Serialization ® Serialization Using Business Objects ® Assign Message Type to a Business Object (transaction BD104). Assign the message types relevant for serialization to each business object type.
3.       In Customizing (IMG) activate the serialized distribution in both the sending and receiving systems:
ALE Implementation Guide (transaction SALE)
Modeling and Implementing Business Processes
Master Data Distribution
Serialization for Sending and Receiving Data
Serialization Using Business Objects
Execute activities Activate Outbound Business Objects and Activate Inbound Business Objects. Set the Serialization flag for the required business object types.
If you want to do serialization by message type then
1. go to BD44 and create a serialization group and assign messages and the serial number to each.
2. Run the program RBDSER01.
Award points if useful,
Aleem.

Power View in SharePoint Server - The data extension type for a data source is not valid

Hi All,
All of a sudden I am getting following error when trying to create Power View report using shared report data source (no error testing the connection):
"The current action cannot be completed. The data extension type for a data source
'http://dev/Shared Ducuments/Sales.rsds' is not valid for this operation"
I already have a data source (I had created it after creating my site collection a week ago) and when I use this source to create Power View report then there is no error but I am getting above error when I create another similar data source and use it to create
a Power View report.
Please help me to resolve the error.
Thanks

I am going nuts! I had selected 'Analysis Services' instead of 'Microsoft BI Semantic Model for Power View'

RSAR2318 : IDoc type for source system T90CLNT090 is not available

Hi all,
I am working on BI + ECC 6.0. Have created a ODS object using RSA1OLD. While activating the ODS, am getting this error:
1. Error:
R7I028
Object could not be activated
2. Error:
RSAR238
IDoc type for source system T90CLNT090 is not available
Error when creating the export datasource and dependent objects
Error RSAR238 : IDoc type for source system T90CLNT090 is not available
I have already checked trx & dtps, but could not find resolution.
Kindly help me with this error.
Thanks and regards,
MS

M Sharma wrote:
But how exactly can I create when T90CLNT is not active? Help please.
Yes, you would need to check with BASIS team how they have created an alternate source system (for debugging) & prepare a RFC b/n these systems. Can you just check the settings in the source system and BI source system...and check the source system for the same BI system. Right click > Check and then do a restore or take the help of basis to fix it. What I think is a possible solution is : RSA1 > Source system > Search System > Right Click > Activate

RSAR238 : IDoc type for source system T90CLNT090 is not available

Hi all,
I am working on ECC 6.0. Have created a ODS object using RSA1OLD. While activating the ODS, am getting this error:
1. Error:
R7I028
Object could not be activated
2. Error:
RSAR238
IDoc type for source system T90CLNT090 is not available
Error when creating the export datasource and dependent objects
Kindly help me with this error.
Thanks and regards,
Dhanapal

Hi,
Check the same in SDN..
Object ZDUMMY could not be activatedMessage no. R7I028
Re: DSO Activation problem
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/test-cases-for-module-human-capital-management-1425016
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/idoc-type-for-source-system-t90clnt090-is-not-available-message-no-rsar238-1431565
Thanks
Reddy

Confusion on IDOC types for creation of PO

Hi,
Requirement is sending PO from sendin SAP system to receiving system.
For sending am using-
Processing code ME10
On serching forums and tutorials, i came across IDOC type- ORDERS05 but this idoc type is for both PO and SO.
PORDCR04 idoc type for creation of PO only.
Some post says PORDCR04 doesnt create PO header text.On the other hand,For inbound processing of PO idoc ( using ORDERS05 ) processing code is not available.
I will be thankful if somebody can guide me which of these idoc types is preferable.
Thanks.
Edited by: Sanjay_lnt on Jan 8, 2011 3:49 PM

Hell Sanjay
Outbound ORDERS (= Purchase Order) and inbound ORDERS (= Sales Orders) are like siblings which reflect the customer / supplier relationship.
In case of the PORDCR04 IDoc it is somewhat different because does it make sense to have the same purchase order in different system?
In our case a POS (= point of sales) system is used to create a purchase order (for replenishment) which is then converted (via SAP-PI) into an inbound PORDCR04 IDoc in the ERP system. Out of this purchase order a replenishment delivery (for the shops) is created.
Regards
Uwe

Standard idoc type for Vendor invoices

Hi All,
Can anyone tell me if any <b>standard idoc type for Vendor invoice(Cleared items)</b> exists and if any standard report is there to populate and distribute that idoc?
I want the fields bukrs,belnr,lifnr,bldat,cpudt,zfbdt,zterm,xblnr,waers,dmbtr and mwsts in that standard IDOC.
Thanks in advance

Hi,
check this IDOC types..
SINGLEREMUNRQS_CREATE01 "46A
SINGLEREMUNRQS_CREATE02 "620
regards
vijay

Standard IDoc Type for Inbound NonPO Vendor Invoices - FB60

What should be the perfect standard IDoc Type for Inbound NonPO Vendor Invoice posting. Tcode FB60.
I found IDoc Type FIDCCP02 but the Function Module 'IDOC_INPUT_FIDCC2' for FIDCCP02 is not released.
In the same way many other standard function modules like - IDOC_INPUT_ACLPAY, IDOC_INPUT_FIDCCH, IDOC_INPUT_ACC_INVOICE_RECEIPT and few more are not released.
My question : If at all I have to use standard IDoc Type, Message type and Function module (Released) for Inbound NonPO Vendor Invoices, then what should be the solution from SAP ?
Thanks,
Veeru.

Hi,
IDOC_INPUT_FIDCC2 for FIDCCP02 works for us in ECC6.0
If you want Automatic tax calculation functionality using FIDCCP02.. then FIDCC2 is not correct message type for you. In that case you should probably go for :
Msg: INVOIC
Basic type: INVOIC02
FM: IDOC_INPUT_INVOIC_FI
Process code: INVF
Thanks,
Kumar

Incorrect MIME type for XML Data Connection POST requests

It appears that Xcelsius 2008u2019s XML Data Connection logic does not specify the correct MIME type for the data it sends to the server in its POST request. Using an HTTP debug proxy, I was able to see that Xcelsius sends XML data in the POST, but is setting a content-type of u201Cx-www-form-urlencodedu201D. According to the W3C spec:
http://www.w3.org/TR/html401/interact/forms.html#h-17.13.4.1
Data sent with a MIME type of u201Cxxu201D should be encoded as key?value pairs, like this:
key1=val1&key2=val2&Submit=Submit
So, what Xcelsius is doing is clearly incorrect. Worse, if your server process is a Java servlet, you may find that the POSTed data will be gobbled up by the servlet container and you wonu2019t be able to read it using a getInputStream(), or getReader() call because itu2019s already been processed by a call to the getParameter() method.
The correct mime type for POSTing an XML formatted request from Xcelsius should be "text/xml".
Wayne

Hi,
The Error #2032 your getting is due to the Flash player security.
To remove this this error you need one crossdomain Xml file in the root directory which actually provides a lot more control over who has access to your data from a SWF. The cross domain policy is attached as crossdomain.xml.
In the XML file, it is used a wildcard (*). This allows a SWF located on any machine to access your data source. You can certainly use an IP address or domain name to restrict access rather to opening it up completely. I always start with the wildcard to make sure my dashboard works, then start restricting access as necessary.
Here is a whitepaper with everything you need to know about Flash player security:
http://www.adobe.com/devnet/flashplayer/articles/flash_player_9_security.pdf
Please let me know if you need any more clarification.
Regards,
Sanjay

Idoc Type for Organization Data

Similar Messages

Maybe you are looking for