TCode

[Former Member]

Can anyone tell me what is TCode file used for and how is it usefull in ensuring delivery of the file

[Former Member · Accepted solution]

Hi,

Sry i posted list of all TCODES

The T-Code FILE is used to define 'Logical File' and to map 'Logical File' with 'Physical File Path'.

Thanks

Vikranth

[Former Member · Accepted solution]

Does this Logical file anyhow related with the actual files which we are sending over XI.

Where else does XI stores the name of the file which we have sent?

[Former Member · Accepted solution]

Hi,

Logical file is not a actual file physical file is the actual file but you will link your physical file to logical file and then you will send your logical file to XI system.

Thanks

Vikranth

[Former Member · Accepted solution]

Should the name of physical file and logical file must be same?

Do you know the table name where these file name get stored?

[Former Member · Accepted solution]

Hi,

Should the name of physical file and logical file must be same?

no you can have different names for physical and logical file.

Do you know the table name where these file name get stored?

Table name : V_FILEPATH

Thanks

Vikranth

[Former Member · Accepted solution]

Thanks for the reply

If file path for logical file is not created using Tcode FILE,

is there any table where the name of the file is stored whose path is mentioned in sender communication channel ?

[Former Member]

Hi,

COMPLETE SAP XI TRANSACTION CODES

ALRTCATDEF- Alerts Configuration.

ALRTDISP - Display of Alerts Created

SXMB_IFR -> Start Integration Builder

SXMB_MONI -> Integration Engine - Monitoring

SXI_MONITOR -> XI: Message Monitoring

SXI_CACHE -> To Access IS runtime cache

SXI_SUPPORT -> Test all the Repository and Directory Objects

SXI_CACHE -> XI data directory cacheidx1 -> idoc adapter

IDX2 -> idoc metadata

IDX5 -> monitocr idoc adapter

SM21 -> log di sistema

ST22 -> dump abap (analisi di eccezioni)

SMQ1 -> messages inbound e outbound queue

SMQ2 -> messages inbound e outbound queue

SMICM -> J2EE administration

ST06 -> stato della macchina cpu memory filesystem machine status - cpu, memory and file system.

ST03 -> workload.

SCC4 -> visualizza mandanti del sistema

WE20 -> partner profiles

sale - ale settings

RZ10 - edit system profile

SM59 ->mantain rfc destinations

BD64 -> mantain distribution model (trasformazioni)

SU01 -> users

AL08 -> list all logged users(user login logon)

SE10 -> Change Request

SE09 -> Change Request

WE05 -> All idocs

WE19 -> IDoc Test Tool

WE21 -> port definition

SE11 -> Data dictionary

SM21 -> log sistema xi

se37 -> mantain funcion modules

SICF -> http server configuration

SMGW -> trace, alzare livello di trace.

BD13 ->

BD64 -> modelli di distribuzione

PFCG -> Roles

tabella TSTC -> sap transactions codes

tabella TSTCT -> transaction descriptions

STMS -> transports management

SPAM -> apply ABAP support packages

SPAU -> manage objects after apply support packages

SE01 -> manage change requests

SLDCHECK -> Test SLD Connection

SLDAPICUST-> SLD API Customizing

SXMB_ADM -> Integration Engine - Administration

SXMB_MONI_BPE -> Process Engine - Monitoring

SE38 -> ABAP Editor

SE11 -> ABAP Dictionary

ST22 -> ABAP dump analysis

SPROXY-> ABAP Proxy Generation

SE80 -> Object Navigator

ABAPDOCU -> ABAP Documentation and Examples

SE24-> Class Builder

SM21-> Online System Log Analysis

SMQ1-> qRFC Monitor (Outbound Queue)

SMQ2-> qRFC Monitor (Inbound Queue)

RZ70-> SLD Administration

SM58-> Asynchronous RFC Error Log

SM59-> RFC Destinations (Display/Maintain)

SMICM-> ICM Monitor

WE60-> Documentation for IDoc types

BD87-> Status Monitor for ALE Messages

IDX1-> Port Maintenance in IDoc Adapter

IDX2-> Meta Data Overview in IDoc Adapter

WE05-> IDoc Lists

WE02-> Display IDoc

WE19-> Test tool

WE09-> Search for IDocs by Content

WE20-> Partner Profiles

WE21-> Port definition in XI

SE16-> Data Browser

SE93-> Maintain Transaction Codes

SM30-> Call View Maintenance

SU01-> User Maintenance

SM02-> System Messages

BD54 -Logical System Creation.

SWXF_PBUILDER -> for Detail BPM Process

SMQS - > to register the destination in QOUT scheduler

WEOUTQUEUE - > to start the queue processing

SMQR - > to register the queue

IDXPW - > to activate the IDOC message package

IDXP - > to monitor the message packages.

SWF_XI_CUSTOMIZING -> transaction to check prerequisites for integration processes

Thanks

Vikranth

[Former Member]

Thank you Khimawat

Although you did'nt answered my question but your answer is very help full.

Do you have any info about TCode "FILE" too?

[aashish_sinha]

Hi,

Its used in SAP ARchiving

1. You can use Tcode DB15 to identify which archiving object is associated with which tables of your database.

2. Find out in TCode FILE whether there is physical path p=<dir_global>/filename defined for the logical path <archive_global_path> and if there is a physical file definition <paramX_date_time.archive> for the logical file definition <archive_data_file>

3. Use TCode SARA to write your tables of the archiving object from the database to archive physical archive file defined in point 2. Choose the archiving object .

First chose Technical settings---> customizing object specific ---> and execute.

Hope this will help you.

Regards

Aashish Sinha

PS : reward points if helpful

[Former Member]

Hi,

check the following:

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/xi%2btransaction%2bcodes

also these

ALRTCATDEF -> Alerts Configuration

ALRTDISP -> Display of Alerts Created

SXMB_IFR -> Start Integration Builder

SXMB_MONI -> Integration Engine - Monitoring

SXI_CACHE -> XI data directory cache

SXI_MONITOR -> XI: Message Monitoring

SXI_SUPPORT -> Test all the Repository and Directory Objects

IDX1 -> idoc adapter

IDX2 -> idoc metadata

IDX5 -> monitor idoc adapter

SMQ1 -> Outbound queue monitoring

SMQ2 -> Inbound Queue Monitoring

SMQR, SMQs -> Registration of queues

SMICM -> J2EE administration

SALE -> configuration

PFTC -> Workflow builder

SM59 -> maIntain RFC destinations

SICF -> http server configuration

SMGW -> Gateway trace

SLDCHECK -> Test SLD Connection

SLDAPICUST-> SLD API Customizing

SXMB_ADM -> Integration Engine - Administration

SXMB_MONI_BPE -> Process Engine - Monitoring

SPROXY-> ABAP Proxy Generation

SE80 -> Object Navigator

RZ70-> SLD Administration

SM58-> Asynchronous RFC Error Log

SWXF_PBUILDER -> for Detail BPM Process

WEOUTQUEUE - > to start the queue processing

IDXPW - > to activate the IDOC message package

IDXP - > to monitor the message packages.

SWF_XI_CUSTOMIZING -> transaction to check prerequisites for integration processes

Thanks

Vikranth

[Former Member]

Hi,

tcode is a transaction code. The most important tcodes for xi are listed here:

/people/morten.wittrock/blog/2006/03/23/getting-started-with-xi-part-1-xi-30-cheat-sheet

Regards

Patrick

[Former Member]

I am talking about a TCode called "FILE"

Does someone has any information about it?

[Former Member]

Hi,

sorry for that misunderstanding!

Found just two threads about it:

Regards

Patrick

[GabrielSagaya]

Using the FILE Transaction

You can set up a logical file name and then link this to a physical file.

Also you can access the physical file folder

[Former Member]

Hi,

Can you be more clear?

Regards

Bhanu