Add conversion rule in SCOT

Hello all,
Can any one please help me with how to add conversion rule in SCOT to convert .ali file format to .csv file format?
Thanks in advance.

Hi,
Please find below link. May be these are helpful to you.
http://scn.sap.com/thread/717106
http://help.sap.com/saphelp_nw70/helpdata/en/af/73563c1e734f0fe10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/39/4d3d3d9ba00645e10000000a114084/content.htm
Regards,
Saket S. Ghanekar

Similar Messages

How to add conversion rule in SCOT email attachment.

Hello All,
How to add conversion rule in SCOT email attachment.
I try to csv conversion rule in scot through spro. I add this rule through SPRO successfully but this rule not added in SCOT internet tab.

Hi,
Please find below link. May be these are helpful to you.
http://scn.sap.com/thread/717106
http://help.sap.com/saphelp_nw70/helpdata/en/af/73563c1e734f0fe10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/39/4d3d3d9ba00645e10000000a114084/content.htm
Regards,
Saket S. Ghanekar

Add csv format in scot

Hello all,
I am working on ECC 6.0 and I want add CSV file format in output file format of SCOT T-code.Can any one tell me how to add this format in SCOT.
Thanks in advance.

i found this string on net
add a Conversion-rule (transaction SCOT like this:
CSV CSV 1 SX_OBJECT_CONVERT_TXT_INT
How i Add .

SCOT conversion rule

Hi,
What is the usage for the conversion rule under Tcode: SCOT. Since, i faced a problem that the outgoing email attachment always converted to TXT file( By my ABAP program with FM SO_NEW_DOCUMENT_ATT_SEND_API1). Could i do some changes in this area??
Regards,
Kit

Hi,
You can use printing using e-mail to send data as an attachment to an e-mail. The recipient can then display and/or print the data.
All device types can be used to print the e-mail. However, you must ensure that the relevant display program or printer is available for the device type. We recommend that you use device type pdf1, as with pdf1, a PDF file is generated from the document, and sent as an e-mail attachment. You can then display this with a PDF display program, such as Adobe Acrobat Reader, and print it as required.
Prerequisites
·        As of SAP Web Application Server 6.10, you must have activated and configured the interface to send e-mails from the SAP System in SAPconnect (transaction SCOT). For more information, see the Guidelines for SMTP Configuration. These guidelines explain, among other things, how to create an SMTP node in transaction SCOT, which can be used without special additional settings for e-mail printing.
Up to SAP Basis 4.6D, communication is performed using an additional external communication system and, accordingly, a SAPconnect node with the corresponding RFC connection must be set up until SAP Basis 4.6D (inclusive).
·        So that the recipient not only receives the mail, but can also reply using the REPLY button, you must maintain the e-mail addresses for all users in the user maintenance transaction SU01.
If you are using a default domain in transaction SCOT, the mail is sent, but the relevant user cannot reply using the reply button, as the generic sender address does not really exist.
·        You must have created a device definition for printing using e-mail in the SAP System.
·        To print using e-mail, the sender must, in addition to the usual authorization for the output device, also have authorization for the (pseudo) output device %MAI.
With this authorization, you can easily remove the right to use devices with access method M from individual users.
also check the below link
http://help.sap.com/saphelp_nw04/helpdata/en/39/4d3d3d9ba00645e10000000a114084/content.htm
Regards,
Nagaraj

Errors with the global conversion rule for the field 0SOURSYSTEM.

Hello Gurus,
We are implementing CRM Activities. I enhanced the data source and when I add new info objects to 0SAL_DS01 DSO and trying to activate I'm getting there errors. Can some one please help me out in this problem?
Error in global conversion rule for InfoObject 0SOURSYSTEM
Message no. RSAR263
Diagnosis
Errors with the global conversion rule for the field 0SOURSYSTEM.
System Response
The function module delivers the following error message:
Field "" is unknown. It is neither in one of t
Procedure
Check the definition of the global conversion rule for an InfoObject
What does this error mean? We are using BI 7.
Thanks
RKR

I have around 9 source systems, do I have to maintain data for all of them for 0SOURCESYSTEM?
I set data for CRM system and then tried to activate.. but still I'm getting same error.
I;m getting this warning too...
InfoObject 0FISCVARNT needs to be in key for DataStore object C_0SAL_D
Message no. RSDODSO123
Diagnosis
Characteristic 0FISCVARNT is included in the data part of ODS object C_0SAL_D.
System Response
The fiscal year variant cannot be used in the update rules for calculating business hour characteristics.
Does this matter???
Thanks
RKR
Message was edited by:
RKR M

Maintain Field Mapping and Conversion Rules//LSMW

Hello Friends,
I want to add new fields in the step.no.5(Maintain Field Mapping and Conversion Rules).
Indetail i'm going to upload the GL balances, for DR and CR line item fields are same so system is not accepting the same field value, so i have added 1 for the CR line item fields like in the below example.
BSEG-WRBTR(Dr line item)
BSEG-WRBTR1(Cr line item)
but BSEG-WRBTR1(Cr line item) field not displaying in the step.no.5 to mapping to source field.
please let me know the solution for this.
thanks
swapna.

Hi,
I would like to ask few questions.
1. Are you using batch input recording or using any program for uploading. (through LSMW)
2. Whether all your debit or credit line items are same every transactions. I believe they should be same, because you are uploading the balances.
You should not have two similar fields for example, if it is WMBTR, then again WMBTR should not be there, it should WMBTR1 and WMBTR2. Make sure you have done the field mapping properly. When you have done the field mapping all the fileds must have been mapped. If any one of the fields are not mapped, then it will not be uploaded.
Please see the following LSMW sample guide:
http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc
Maintain Object Attributes Do the recording - Make sure that you do not have two fields with the similar name. If you have two fields with the same name double click on the field name and add1 or 2 to differentiate between field names. Just Copy those fields and descriptions in excel sheet, delete the blank lines, then in excel data => text to columns, your field names and descriptions will be now in two columns. Copy them, then put your cursor on the next sheet, then edit => Paste Special => Transpose, all the columns will become your rows. Now your file structure is ready. Maintain Source Structures Give some unique structure name and description Maintain Source Fields Here you add the fields that are being used in EXCEL first sheet, just copy them and make all the fields as C (Constant) and then give length of 60 for all fields. Maintain Structure Relations Though structure relations are already created just go to this step, click on edit, then click on create structure relation, just accept the message stating that the structure relation has already been created. Maintain Field Mapping and Conversion Rules Do the field mapping for all the fields, all the fields willl be stretched and you will see five rows against each row. In case if there is any row that has NOT stretched means, there is something wrong in the mapping. Maintain Fixed Values, Translations, User-Defined Routines There is nothing to be done at this step. You can simply ignore this. Specify Files Make you must have saved your excel file as .txt (before saving make sure you have copied data from sheet2 to sheet 3 and then sheet 3 is saved at tab delimited file. Text (Tab delimited) Select your file, make SURE that you have select "TABULATOR" radio button and say OK. Assign Files Go to this step and click on Create assignment button and accept the message and say ok. Read Data Remove two check boxes and just click on execute button. See the log. Make sure you have number of entries (lines) in your excel file are matching with this. Display Read Data Display data give 1 to 999 lines and double click on one of the line and see whether fields are mapped correctly are not. Convert Data Execute and see the log match the number of entries. Display Converted Data Display converted data, give 1 to 999 and double click on one of the line and see whether fields are mapped correctly or not. Create Batch Input Session Check on Keep Batch Input sessions check box, then execute. If you select that check box, even after execution it will be there and you can analyze what happened. Run Batch Input Session (Takes you to SM35) Go to SM35 select the batch and click on process button (execute), make sure you have checked right hand side first three check boxes and FOREGROUND (because you want to save what it is creating) Say OK Keep on press ENTER on your key board in order to move the session further. If you follow these steps along with the guide, surely you should be successful. There may be small difference between the file and what I have explained but ultimately the purpose is same. Hope this is useful and let me know in case if you have any issues.
Regards, Ravi

Idoc conversion rule

Hi,
What is idoc conversion rule? Why we need this?
While upgrading from 4.7 to ECC 6.0 what all precautions need to be taken for the existing standard idocs and custom idocs in the system.
Thanks & Regards,
Soumya.

Hi,
ALE allows the user to perform an SAP transaction in the sending system, after-which the following steps occur:
1 or more communication IDocs (intermediate documents: container for the application data) are created in the sending system database. An ALE distribution model, that needs to have been configured, determines which systems the IDocs are to be sent
These communication IDocs, that contain the relevant application data of the transaction that was performed, are then passed to the ALE communication layer
This layer performs an RFC call, using the port definition and an RFC destination determined through the customer model
The IDocs are then transferred to the respective receiving systems. These could be SAP R/3, R/2 or external systems
If the receiving system is an SAP system then:
In the case of master data distribution the same transaction that was performed on the sending system is again performed on the receiving system with the data contained in the IDoc. This allows the data to go through the SAP checks before posting occurs
In the case of transaction scenarios the relevant data is passed to the respective transactions in order to load the required application document. Eg. A PO is loaded on the sending side, yet a SO is created on the receiving system
Master data has another difference:
It can be set up in such a way that any changes made to specific fields in master data tables can automatically trigger off the ALE distribution process for that particular master data object
If a master data object is created or changed on a sending system and distributed to another system the respective transaction is used to either create or change that respective master data object on the receiving system
In general, if standard SAP can't perform the task required then neither can ALE. It doesn't add functionality, it merely decouples it and allows you to distribute it onto other remote systems.
The Detail as described by SAP
In the output processing one of the function modules of the application creates an IDoc, the so-called master IDoc. This IDoc is sent to the ALE layer where the following processing steps are applied:
Outbound processing
Receiver determination
An IDoc is similar to a normal letter in that it has a sender and a receiver. If the receiver has not been explicitly identified by the application, then the ALE layer uses the customer distribution model to help determine the receivers for the message.
The ALE layer can find out from the model whether any distributed systems should receive the message and, if so, then how many. The result may be that one, several or no receivers at all are found.
For each of the distributed systems that have been ascertained to be receiver systems, the data that is specified by the filter objects in the customer distribution model is selected from the master IDoc. This data is then used to fill an IDoc, and the appropriate system is entered as receiver.
Data selection
Segment filtering
Individual segments can be deleted from the IDoc before dispatch by selecting Functions for the IDoc processing -> Settings for filtering in ALE Customizing. The appropriate setting depends on the sending and receiving logical R/3 System.
Field conversion
Receiver-specific field conversions are defined under Functions for the IDoc processing -> Conversions.
General rules can be specified for field conversions; these are important for converting data fields to exchange information between R/2 and R/3 Systems. For example, the field "plant" can be converted from a 2-character field to a 4-character field.
The conversion is done using general EIS conversion tools (Executive Information System).
Version change
SAP ensures that ALE functions between different R/3 System releases. By changing the IDoc format you can convert message types of different R/3 releases. SAP Development use the following rules when converting existing message types:
Fields may be appended to a segment type;
Segments can be added;
ALE Customizing keeps a record of which version of each message type is in use for each receiver. The correct version of the communication IDoc is created in the ALE output.
The resulting IDocs (it is possible that several IDocs could be created in the receiver determination) are referred to as communication IDocs and are stored in the database. The dispatch control then decides which of these IDocs should be sent immediately. These are passed to the communications layer and are sent either using the transactional Remote Function Call (RFC) or via file interfaces (e.g. for EDI).
If an error occurs in the ALE layer, the IDoc containing the error is stored and a workflow is created. The ALE administrator can use this workflow to process the error.
Inbound processing
After an IDoc has been successfully transmitted to another system, inbound processing is carried out in the receiver system, involving the following steps in the ALE layer:
Segment filtering
Segment filtering functions the same way in inbound processing as in outbound processing.
Field conversion
Specific field conversions are defined in ALE Customizing.
The conversion itself is performed using general conversion tools from the EIS area (Executive Information System).
Generalized rules can be defined. The ALE implementation guide describes how the conversion rules can be specified.
One set of rules is created for each IDoc segment and rules are defined for each segment field.
The rules for converting data fields from an R/2-specific format to an R/3 format can be defined in this way. An example of this R/2 - R/3 conversion is the conversion of the plant field from a 2 character field to a 4 character field.
Data transfer to the application
Input control
When the IDocs have been written to the database, they can be imported by the receiver application.
IDocs can be passed to the application either immediately on arrival or can follow in batch.
You can post an inbound IDoc in three ways:
by calling a function module directly: A function is called that imports the IDoc directly. An error workflow will be started only if an error occurs.
by starting a SAP Business Workflow. A workflow is the sequence of steps to post an IDoc.
by starting a work item A single step performs the IDoc posting.
The standard inbound processing setting is that ALE calls a function module directly. For information about SAP Business Workflow alternatives refer to the online help for ALE programming.

How to add email id in scot

Hi,
Could you tell me how to add email id in scot.
Regards,
Amar

Hi Amar,
Please check this link.
http://help.sap.com/saphelp_nw70/helpdata/EN/2b/d925bf4b8a11d1894c0000e8323c4f/frameset.htm
Hope this will help you..
Regards

Data records in an IDoc getting erased, when conversion rules are defined

Hello ,
We are sending IDocs of message type GLMAST & COELEM from a system(version 4.7) to another system (version 4.6B).
The segment data in the IDocs are changed using the user exit enhancement KKCD0001. The function exits used are EXIT_SAPFKCIM_001 and EXIT_SAPFKCIM_002.
If there is no conversion rule defined in the receiver system, for the segments, the IDocs are posted correctly in the receiving system. But if we define conversion rules , then the data records for all the segments for which conversion rule is defined are getting erased, and an error occurs during processing of IDocs
Please let me know what can be the the reason behind this issue..And how to solve this..
Thanks in advance,
Afsar

Issue solved

Error in global conversion rule for InfoObject 0PERSLANGU when activating

Dear Experts
We are working on HR in BI7.0 with Ehp1.
I am trying to Activate the Transfer Rules of 0HR_PA_PA_1 DataSource which has the BID (BW Development) as the Source System to itself in order to load 0PAPA_C02 (Headcount) InfoCube.
When trying to Activate, it gives the following error message:
Error in global conversion rule for InfoObject 0PERSLANGU
Message no. RSAR263
Diagnosis
Errors with the global conversion rule for the field 0PERSLANGU.
System Response
The function module delivers the following error message:
Incorrect statament: Expression missing Operand mi
Procedure
Check the definition of the global conversion rule for an InfoObject.
In fact, we are Re-implementing 3.0b BW System in new BI7.0 Ehp1 System. I have checked the Config of InfoObject 0PERSLANGU to the one available in existing BWP (3.0b Production) system and it's all the same.
Has anyone come across similar error message and how did you resolve. Any help is very much appreciated.
Many Thanks,
Chandu

HI Chandu ,
It is a bug in the system , can you take a look at the SAP note
Note 1070702 - RSAR 263: Error in global conversion rule for InfoObject
Hope it helps ,
Regards,'
Sathya

Error in global conversion rule for InfoObject 0INCOTERMS2

When I activate BI content 2LIS_12_VCITM with transfer rule, The transfer rule was error with the message " Error in global conversion rule for InfoObject 0INCOTERMS2" and Mgs No. 263.
The transfer rule cannot be activated.
I checked the 0INCOTERMS2 infoObject . The global conversion rule is no error.
The global conversion is in below.
============================================================
PROGRAM CONVERSION_ROUTINE.
Type pools used by conversion program
TYPE-POOLS: RSD, RSARC, RSARR.
TYPES: DE_0INCOTERMS2(000028) TYPE C.
Conversion rule for InfoObject 0INCOTERMS2
    Data type       = CHAR
    ABAP type       = C
    ABAP length     = 000028
FORM CONVERT_0INCOTERMS2
USING    RECORD_NO LIKE SY-TABIX
           SOURCE_SYSTEM TYPE RSA_LOGSYS
           IOBJ_NAME TYPE RSIOBJNM
CHANGING RESULT TYPE DE_0INCOTERMS2 " InfoObject value
           RETURNCODE LIKE SY-SUBRC.
$$ begin of routine - insert your code only below this line        -
TRANSLATE RESULT TO UPPER CASE.
$$ end of routine - insert your code only before this line         -
ENDFORM.
=================================================================
If you have any idea or face the similar problem, please suggest solution.
Thank you.

Good afternoon,
If you have not done so already can you apply the SAP note 1387854 in your system and it should prevent the problem from happening again. If you also reactivate the infoobject 0INCOTERMS2 in RSD1 then it should be possible to manually activate the transfer rule.
Best Regards,
Des

Mail crashes when I try to add a rule

I'm running 10.6.8. I have a somewhat large and complex mail folder. Everytime I try to add a rule mail gives me the spinning beach ball of death. I'm tried throwing away the rule plist. I've tried a clean install on a new disk with nothing on the disk added except firefox and flash. I've been on the phone with Applecare numerous times. Anyone have any ideas? Should I just give up?
Does anyone know if Mail has a size limit for mail or for how many layers folders can be nested?
Keith Sanborn

can't make much of this crash log but try this. when you get to the smtp server page in setup assistant hold option while clicking "create" or 'continue". this will skip the actual server validation and might prevent crashing.

Conversion rule executed in sender and receiver system?

Hello experts,
I want to send an Idoc from one SAP system to another.
Both systems are in the same transport line.
In the sender system I want to execute a field conversion. There
Therefore I maintained BD62 (Define Conversion Rule), BD55 (activate Conversion Rule for Sender/Receiver combination) and BD79 (Specifie Conversion).
The mapping works perfectly.
The creation of the IDoc and the field conversion work perfectly.
But I get an error in the receiver system.
It seems that this system also tries to execute the fieldmapping, because it has the same BD55 (sender/receiver) settings.
The conversion rule itself does not exist in the receiver system, as these settings are not contained in a transport request.
What is the correct way? Can I customize BD55 not to generate a transport request and maintain this setting only in the relevant system?
Or do I need to maintain BD79 and BD62 also manually in the receiver system?
any hints
Barbara

Hi Barbara,
you have to maintain BD79 and BD62 manually in all receiver Systems.
Kind regards
Werner

Errors with the global conversion rule

Hi Guys,
When I activate the DSO,I get an error "Errors with the global conversion rule".I applied OSS note 1387854.But the problem still persists.I did not find any replies on SDN for this error,so posting it again.
If anyone knows how to proceed,please help! <REMOVED_BY_MODERATOR>
Thanks,
Sri
Edited by: Pravender on Dec 9, 2010 4:51 PM

the error might show due to which infoobject this error is happening.
that particular infoobject might conatin a transfer routine. Open the transfer routine in the infoobject, do a dummy change, save the routine and activate the infoobject, then try activating the DSO.
this might do the trick . Hope this helps.
rgds, Ghuru

Using conversion rule to convert quantity fields

Hi!
I am trying to find a way to use a conversion rule to convert a quantity specified in one unit of measure to the corresponding quantity specified in a different unit of measure. I was trying to use 'Copy sender field' along with a custom 'Special conversion rule'. However, the code to convert quantities requires both the quantity and material number to do the UoM conversion. 'Copy sender field' only allows the transfer of one sender field. Is there a way to transfer two sender field into a 'Special conversion rule'. Any help much appreciated and rewarded. Thanks, Duncan

Hi Duncan,
Try FM UNIT_CONVERSION_SIMPLE.
Regards,
Atish

Add conversion rule in SCOT

Similar Messages

Maybe you are looking for