Required transaction

Hi Experts,
We want to have this following journal entry created after vendor payment made to A/P invoice:
Db Credit Card Payable
Cr Cash / Bank
I am referring to the credit card billing payment. Do I have to change the payable account so that each time I made an outgoing payment to the vendor, the transaction journal entry will have this following JE :
Db Credit Card Payable
Cr Cash / Bank
We are using B1 2007A SP01. Thx in adv.
Andres

Hi Andres.....
This kind of transaction is not possible, instead of credit card payable vendor account should be hit. Even though if you think manually then also not possible. Else you need to define the credit card account as control account for the vendors which is not physible..........
Regards,
Rahul

Similar Messages

The requested operation could not be performed because OLE DB provider "MSOLAP" for linked server does not support the required transaction interface.

I am getting the following error when attempting to INSERT the results of an "EXEC(@MDXQuery) at SSAS LinkedServer":
The requested operation could not be performed because OLE DB provider "MSOLAP" for linked server does not support the required transaction interface.
Here is code that illustrates what I am doing:
DECLARE @MDX varchar(max);
SET @MDX='
SELECT
[Measures].[Extended Service Count]
} ON COLUMNS,
NON EMPTY [Organization].[By Manufacturer].[Manufacturer]
ON ROWS
FROM (
SELECT
{[Organization].[Org Tree].&[2025],[Organization].[Org Tree].&[2040]} ON 0
FROM [MyCube]
/* Test 1 */
EXECUTE(@MDX) at SSASLinkedServer;
/* Test 2 */
DECLARE @ResultsB TABLE (
Manufacturer varchar(255)
, ExtendedServiceCount float
INSERT INTO @ResultsB (Manufacturer, ExtendedServiceCount) EXECUTE(@MDX) at SSASLinkedServer;
Test 1 succeeds, returning expected results, and Test 2 fails returning the error mentioned above.
Other articles I've found so far don't seem to apply to my case. I am not creating any explicit transactions in my code. When I use OPENQUERY, I am able to do the insert just fine, but not when I use EXEC @MDX at LinkedServer.
Unfortunately in some variations of the query, I run into the 8800 character limit on OPENQUERY, so I need to use this other approach.
Any ideas?
-Tab Alleman

Hi Tab,
In this case, SQL Server Analysis Services doesn’t support Distributed Transactions by design. Here is a similar thread about this issue for your reference, please see:
http://social.technet.microsoft.com/Forums/en-US/8b07be45-01b6-49d4-b773-9f441c0e44c9/olaplinked-server-error-msolap-for-linked-server-olaplinked-server-does-not-support-the?forum=sqlanalysisservices
One workaround is that use SQLCMD to execute the EXEC AT command and saved the results to a file, then import using SSIS.
If you have any feedback on our support, please click
here.
Regards,
Elvis Long
TechNet Community Support

How to give #ejbCreate 'Required' transaction semantic

I'm can't get the #ejbCreate method on my BMP Entity to provide the 'Required' transactional semantic. The need is for a client to have a transaction that updates several EJBs and also creates one. But I'm finding that if the transaction rollsback the #ejbCreate is still persisted.
I have defined 'create' mewthod to be 'Required' in the container-transaction element of the deployment descriptor but this has not helped. Ie
<container-transaction>
<method>
<ejb-name>Order</ejb-name>
<method-name>create</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
The updates are clearly not affected because they are only persisted when #store is called which only happens if the transaction commits. But all the examples I have ever seen actually inserts DB records during #ejbCreate, and this seems to be happening in its own transaction - though I don't know why and haven't been able to actually confirm that in any case.
I'd really like to know how to declaratively define the appropriate transaction semantic, but failing that I was wondering if anyone knew whether it is safe to move the persistence for #ejbCreate into #store and just have #ejbCreate determine the PK?

Its definitely the create that I want to define as having the "Required" semantic.
It doesn't seem to matter where I call it from (a SSB method with Required transaction or Struts Action that explicitly demarcates transaction), the #ejbCreate does not seem to join to the containing transaction - which it what is required (no pun).
Here is the code from #ejbCreate.
getDao()#create gets a JDBC connection and inserts a record into the DB.
public OrderPK ejbCreate (OrderModel aModel)
throws EjbCreateException {
log.debug("EjbCreate " + aModel);
model = aModel;
try {
return getDAO().create(aModel);
} catch(Exception ex) {
throw new EjbCreateException(null,ex,context);

Problem using passivateStateForUndo when having taskflow requires-transacti

HI All,
i'm trying to use oracle.jbo.server.ApplicationModuleImpl.passivateStateForUndo / activateStateForUndo methods to make and restore some application savepoints.
The problem is that, when i try to use these methods from adf bounded taskflow, (placed on a page as a region ) i receive:
java.lang.NullPointerException
at oracle.jbo.server.ApplicationModuleImpl.passivateStateForUndo method
I made some investigation of the problem and founded that this NullPointerException is caused by taskflow transaction settings "requires-transaction"
If i put the taskflow transaction setting on default , no exception is thrown and passivateStateForUndo / activateStateForUndo methods worked fine.
Is that a bug, and does somebody have an idea how can i solve this ?
I work with TP4.
Regards,
Krasimir

Hi,
why don't you use the declarative save-point feature in taskflows as described in chapter 18 of the documentation ?
"If you want changes the user made within the called ADF bounded task flow to be discarded when it is exited, you can specify the restore-save-point option on the task flow return activity. The ADF Controller will roll back to the previous ADF Model save point that was created when the ADF bounded task flow was entered. The restore-save-point option applies only to cases when an ADF bounded task flow is entered by joining an existing transaction (either the requires-existing-transaction or requires-transaction option is also specified) and a Save Point is created upon entry."
Frank

OLE DB provider "Microsoft.ACE.OLEDB.15.0" for linked server "(null)" does not support the required transaction interface

Hi All,
I am trying to execute a stored procedure and store its result in an excel.
My query to execute stored proc and store sresults in excel
INSERT INTO
openrowset('Microsoft.ACE.OLEDB.15.0',
'Excel 8.0;Database=C:\TC\DataAnalysisFiles\DataAnalysisResult.xls;OLE DB Services=-4','select * from [Sheet1$]')
EXEC UspUnitTest_Test_CheckDuplicateModelNumberSerialNumber
I am getting error
The requested operation could not be performed because OLE DB provider "Microsoft.ACE.OLEDB.15.0" for linked server "(null)" does not support the required transaction interface.
I have enabled below things by running scripts
sp_configure 'show advanced options', 1;
GO
RECONFIGURE;
GO
sp_configure 'Ad Hoc Distributed Queries', 1;
GO
RECONFIGURE;
GO
EXEC master.dbo.sp_MSset_oledb_prop N'Microsoft.ACE.OLEDB.15.0', N'AllowInProcess', 1
GO
EXEC master.dbo.sp_MSset_oledb_prop N'Microsoft.ACE.OLEDB.15.0', N'DynamicParameters', 1
GO
Please help and let me know if this can be resolved
Supriya Thigale

because OLE DB provider "Microsoft.ACE.OLEDB.15.0" for linked server "(null)" does not support the
required transaction interface.
Hello,
When you insert data from SQL Server into a linked server, then a distributed transaction should be started and here it seems this fails.
See
Distributed Transactions (Database Engine) for more Details +
Distributed Queries
Olaf Helper
[ Blog] [ Xing] [ MVP]

Cmp and required transaction

Hi,
I have a session bean starting a transaction ("requires new" in ejb descriptor),
that bean is calling another session bean which has "required", this one is then
setting some attributes in a CMP (setXxx), that also has required and then it
throws an exception, the first session bean catches it and rolls back. But when
I check in the db the value set by setXxx has been updated, shouldn't the whole
transaction be rolled back?
Thanks,
A.

Hi,
I have a session bean starting a transaction ("requires new" in ejb descriptor),
that bean is calling another session bean which has "required", this one is then
setting some attributes in a CMP (setXxx), that also has required and then it
throws an exception, the first session bean catches it and rolls back. But when
I check in the db the value set by setXxx has been updated, shouldn't the whole
transaction be rolled back?
Thanks,
A.

User exit or BADI for ME22N transaction (please read my requirement)

In me22n transaction when i change a PO Delivery date for any line item and click on save The field latest GR date MEPO1313-LEWED in DELIVERY tab below should display date as per my requirement i.e (delivery date + 90 days)
What uerexit is to be used else if BADI is used pleasee provide me step by step guide as i have never used vadi
IT is urgent. plz helopp.

Hi
Find the available exits with the following program:::
*& Report ZFINDUSEREXIT
report zfinduserexit.
tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
tables : tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode obligatory.
select single * from tstc where tcode eq p_tcode.
if sy-subrc eq 0.
select single * from tadir where pgmid = 'R3TR'
and object = 'PROG'
and obj_name = tstc-pgmna.
move : tadir-devclass to v_devclass.
if sy-subrc ne 0.
select single * from trdir where name = tstc-pgmna.
if trdir-subc eq 'F'.
select single * from tfdir where pname = tstc-pgmna.
select single * from enlfdir where funcname =
tfdir-funcname.
select single * from tadir where pgmid = 'R3TR'
and object = 'FUGR'
and obj_name eq enlfdir-area.
move : tadir-devclass to v_devclass.
endif.
endif.
select * from tadir into table jtab
where pgmid = 'R3TR'
and object = 'SMOD'
and devclass = v_devclass.
select single * from tstct where sprsl eq sy-langu and
tcode eq p_tcode.
format color col_positive intensified off.
write:/(19) 'Transaction Code - ',
20(20) p_tcode,
45(50) tstct-ttext.
skip.
if not jtab[] is initial.
write:/(95) sy-uline.
format color col_heading intensified on.
write:/1 sy-vline,
2 'Exit Name',
21 sy-vline ,
22 'Description',
95 sy-vline.
write:/(95) sy-uline.
loop at jtab.
select single * from modsapt
where sprsl = sy-langu and
name = jtab-obj_name.
format color col_normal intensified off.
write:/1 sy-vline,
2 jtab-obj_name hotspot on,
21 sy-vline ,
22 modsapt-modtext,
95 sy-vline.
endloop.
write:/(95) sy-uline.
describe table jtab.
skip.
format color col_total intensified on.
write:/ 'No of Exits:' , sy-tfill.
else.
format color col_negative intensified on.
write:/(95) 'No User Exit exists'.
endif.
else.
format color col_negative intensified on.
write:/(95) 'Transaction Code Does Not Exist'.
endif.
at line-selection.
get cursor field field1.
check field1(4) eq 'JTAB'.
set parameter id 'MON' field sy-lisel+1(10).
Execute the report, give the transaction you want to find user exit, and query.
BADI
To search for a badi, go to se 24 display class cl_exithandler.
double click on method get_instance, get a break point on case statement.
execute and start the required transaction in new session.
look for variable exit_name. It would show the available badi's.
Please do reward if useful
Regards
Dinesh

To create the follow up transaction automatically on status change in sap crm?

To create the follow up transaction automatically on status change in sap crm? If yes, how to make the setting for this?

Hi vishal,
As per the requirement transaction type is activity(ACTI) & sales order(TA). when the take order objective is complete system automaticaly craete a new activity of tele sales call or metting with wholesaler.
this is requirement of client.
now i am already create all type of transaction types of activity & sales order & create follow up transaction also. i have doam already create action profile also but when i am assign this action profile to transaction & try to create an sales order no follow up transaction could be create automatically. i think the condition is not right so please help me out in this. what should be the start & schedulec condition for this scenerio

JDBC, JMS and EJB transactions - possible problem?

Hello,
          I am using Oracle 9, Weblogic 8.1 SP 4, MyEclipse and
          XDoclet.
          In my current project I have the following piece of code
          in one of my message driven beans (code cited as pseudocode
          without unnecessary details):
          * @ejb.bean name="MyMessageProcessor"
          * display-name="Display name for a MyMessageProcessor"
          * jndi-name="ejb/MyMessageProcessor"
          * description="Bean MyMessageProcessor"
          * destination-type="javax.jms.Queue"
          * transaction-type="Container"
          * acknowledge-mode="Auto-acknowledge"
          * subscription-durability="Durable"
          * generate="false"
          * @ejb.transaction type="Required"
          public class MyMessageProcessor implements MessageDrivenBean, MessageListener {
          public void onMessage(Message msg) {
               try {
                    //obtaining connections to two different databases via JNDi
                    java.sql.Connection connOne =
                    ((DataSource)ctx.lookup("DataSourceOne")).getConnection();
                    java.sql.Connection connTwo =
                         ((DataSource)ctx.lookup("DataSourceTwo")).getConnection();
                    // performing some UPDATEs and INSERTs on connOne and connTwo
                    // calling some other methods of this bean
                    //creating the reply JMS message and sending it to another JMS queue
                    Message msgTwo = this.createReplyMessage(msg)
                    this.queueSender.send(msgTwo);
                    //commiting everything
                    this.queueSession.commit();
               } catch (Exception ex) {
               try {
                    if (this.queueSession!=null) this.queueSession.rollback();
               } catch (JMSException JMSEx) {};
               this.context.setRollbackOnly();
          Some days ago (before the final remarks from my client) there used to be only one DataSource configurated on the basis of the
          connection pool with non-XA jdbc driver. Everything worked fine
          including the transactions (if anything wrong happend not only wasn't the replymessage sent, but also no changes were written
          to database and the incomming message was thrown back to the my bean's
          queue).
          When I deployed the second DataSource I was informed by an error message, that only one non-transactional resource may
          participate in a global transaction. When I changed both datasources
          to depend on underlying datasources with transatcional (XA) jdbc drivers, everything stopped working. Even if
          EJB transaction was theoretically successfully rolledbacked, the changed were written to the database
          and the JMS message wasn't resent to the JMS queue.
          So here are my questions:
               1. How to configure connection pools to work in such situations? What JDBC drivers should I choose?
               Are there any global server configurations, which may influence this situation?
               2. Which jdbc drivers should I choose so that the container was able to rollback the database transactions
               (of course, if necessary)?
               3. Are there any JMS Queue settings, which would disable the container to send message back to the
               queue in case of setRollbackOnly()? How should be the Queue configurated?
          As I am new to the topic and the deadline for the project seems to be too close I would be grateful
          for any help.
          This message was sent to EJB list and JDBC list.
          Sincerely yours,
          Marcin Zakidalski

Hi,
          I found these information extremely useful and helpful.
          The seperate transaction for sending messages was, of course, unintentional. Thanks a lot.
          Anyway, I still have some problems. I have made some changes to the
          code cited in my previous mail. These changes included changing QueueSessions
          to non-transactional. I also set the "Honorate global transactions" to true.
          I am using XA JDBC driver. After setting "Enable local transactions" to false
          (I did it, because I assume that JDBC transactions should be part on the global
          EJB transaction) I got the following error:
          java.sql.SQLException: SQL operations are not allowed with no global transaction by default for XA drivers. If the XA
          driver supports performing SQL operations with no global transaction, explicitly allow it by setting
          "SupportsLocalTransaction" JDBC connection pool property to true. In this case, also remember to complete the local
          transaction before using the connection again for global transaction, else a XAER_OUTSIDE XAException may result. To
          complete a local transaction, you can either set auto commit to true or call Connection.commit() or Connection.rollback().
          I have also inspected the calls of methods of bean inside of onMessage() method just to check, whether
          the transactions are correctly initialized (using the weblogic.transaction.Transaction class).
          My questions are as follows:
          1. Any suggestions how to solve it? I have gone through the google answers on that problem and only
          thing I managed to realize that JDBC must start its own transaction. Is there any way to prohibit it
          from doing that? Can using setAutocommit(true/false) change the situation for better?
          2. How to encourage the JDBC driver to be a part of EJB transaction?
          3. As I have noticed each of ejb method has its own transactions (transactions have different
          Xid). Each method of the bean has "required" transaction attribute. Shouldn't it work in such
          way that if already started transaction exists it is used by the called method?
          4. The DataSources are obtained in my application via JNDI and in the destination environment I will have slight
          impact on the configuration of WebLogic. What is least problematic and most common WebLogic configuration which would
          enable JDBC driver to participate in the EJB transaction? Is it the WebLogic configuration problem or can it be
          solved programmically?
          Currently my module works quite fine when "enable local transactions" for DataSources is set to true, but this way
          I am loosing the ability to perform all actions in one transaction.
          Any suggestions / hints are more than welcomed. This message was posted to jdbc list and ejb list.
          Marcin

How to Put together all SAP Transactions that are used a single User

Dear Friends,
In our client place, each user will be given a set of transaction codes, (like Sales Order Creation, Invoice Creation etc....). Each user role differs with other user role.
Our client requirement is to put together all transaction codes on which his role is assigned, for instance transaction coeds like VA11, VA15N, VA21, VA25N, VL01N, VL06O, Print command. and customer generated report 'Z' codes should be placed together in a single transaction.
I heard about area menus but I dont know how to call that functionality within the Sales Transactions. Could any one of you help me to resolve this issue. Your suggestions will be highly appreciated.
Thank you,
Raghu Ram

HI,
In case of your requirement , you can create an Area Menu (SE43) based on the role and assign all the required transactions.
Later you can assign that Area Menu as the default parameter to the User ID (SU01).
Whenever the user will logon he will see that area menu instead of initial SAP screen.
Please check with the same and confirm.
Regards,
Harsh

Using Portal for streamlining transaction entry

Hello All
We have a client who would like to speak to a company that has used the portal as a "frontend" to transactional entry in ECC. This client is has a resource issue and has found that the transactions in ECC are far greater than their legacy system. If you have a cleint who has imploented such an approach and could speak to lessons learned, etc.. please let me know.
Thanks
Steve
Notes from Customer:
Issue:
The implementation of SAP has inundated the plants with a large number of transactions they did not have to perform previously. No resources have been added to help support this additional day to day transaction load.
Applications:
Active Ingredients Processing, PP, QM, SD
Primary Transactions:
Plan Production (MD01, MD04, MD06), Post Production (COR1/CORK & MFBF), Results recording (QE51n), Post Goods Issue & Post Goods Receipt (MIGO), Create PO & STO to Purchase Raw Mtls (ME21n), Create Deliveries (VL02n), ), Clear Backlog (COGI & MF47). Custom transactions for the following: MIGO 309 & 311 (ZMIGO), Expected Shipments (ZMM003) & Expected Receipts (ZMM004), Delivery Status (ZMM007), Goods Movement Report (ZPP001).
Background:
Prior to SAP production personnel had very few system transactions they were responsible for. Many plants had outmoded computers and poor network connections. The PC skill level varied tremendously from e-mail only capability to superuser. Each plant had their own manual process for tracking inventory, production planning, production recording, shipping, etc. Raw mtl ordering was done via phone call releases against blanket orders. Customer Orders simply showed up on the fax machine and were dealt with as time permitted. Any changes were communicated via phone or refax of change order. The only system data entry was the PGI of shipments which required only 4 or 5 pieces of information. This was done on a daily basis with relative ease since negative inventory was allowed.
Description:
The advent of SAP brought an upgrade to the hardware, software, network connections, and required a large increase in the average PC skill level. In addition, the plants have taken on a huge transaction burden compared to pre-SAP and are struggling to perform all of their required daily tasks (run plants and produce & ship product) and in addition execute all of the required transactions. The larger plants have bigger staffs and can better distribute and absorb some of this load, but the smaller plants have been hit the hardest.

Hi Nilesh,
Depending on the Scenario you need to decide what BAPI you will use. what solution are you excepting?
Regards
Shital

JCA / JDBC Configured for non-XA Attempting XA Transaction Commit

I am attempting to create simple BPEL SOA composites in SOA 11.1.1.5 that use a DbAdapter to execute a stored procedure in an 11g database. The database task being performed only involves a single database and does not require transaction support. I have carefully stepped through the creation of the DataSource and JCA pointing through the DbAdapter to the JDBC DataSource so XA transaction support is disabled, the JCA pool sets the transaction mode to "No transaction" and the JCA pool uses the dataSource value to point to the JNDI name of the JDBC pool rather than the xADataSource value.
Visually,
DataSource definition:
name = jdbc/myserviceDataSource
driver = oracle.jdbc.xa.client.OracleXADataSource
url = jdbc:oracle:thin:@mydbhost.myfirm.com:1521:GENERIC
use XA DataSource = unchecked
set XA timeout = unchecked
Keep XA connection until transaction complete = checked
keep connection after local transaction = checked
JCA definition:
name = eis/DB/myserviceDataSource
dataSourceName = jdbc/myserviceDataSource
xADataSourceName = (blank)
platform class name = org.eclipse.persistence.platform.database.Oracle10Platform
Transaction | Transaction Support: no transaction
This configuration works on one sandbox server and I got it working in a second sandbox server. However, after deleting the JDBC and JCA pools to go through the process one more time to document the procedure on the second server, I am unable to get the configuration working again. The WebLogic domain appears to be resurrecting portions of an old configuration that still references the JNDI name of the JDBC pool in the xADataSourceName parameter. I have unpacked the DbAdapter.rar archive for the DbAdapter and verified the contents of the ./META-INF/weblogic-ra.xml file don't use the xADataSouceName parameter. The Deployment Plan for the DbAdapter (named DbAdapterPlan.xml in $SOA_HOME/soa/connectors ) also explicitly configures the JCA pool using the dataSourceName value leaving the xADataSourceName value blank.
However, executing the SOA service using this JCA connection results in this error:
java.sql.SQLException: Cannot call Connection.commit in distributed transaction.
Again, I know the theoretical answer to this question is to disable transactions in the JCA and JDBC configurations and don't use the xADataSourceName element of the JCA configuration to point to the JDBC pool. However, after validating those elements and restarting the pools or performing an Update on the DbAdapter deployment, WebLogic seems to still create connections through the JDBC pool with transactions enabled.
Any suggestions?
Should I just completely undeploy the DbAdapter and redeploy it from the SOA binary installation directory? These are just lab machines right now so that's obviously not a good long term answer for production use but may help start over with refining a better procedure for doing this.

You should use a non-xa driver for your data source...
From the weblogic docs...
Configure Transaction Options
When you configure a JDBC data source using the Administration Console, WebLogic Server automatically selects specific transaction options based on the type of JDBC driver:
For XA drivers, the system automatically selects the Two-Phase Commit protocol for global transaction processing.
For non-XA drivers, local transactions are supported by definition, and WebLogic Server offers the following options ...
http://docs.oracle.com/cd/E23943_01/web.1111/e13737/jdbc_datasources.htm#autoId8
Cheers,
Vlad

Transactional Context

hi guys
Have a quick question on transactional context
Question:
Will the transactional context be passed on from a LSB mediator to other java
components (simple java classes).
The LSB is delgating control to managers which are simple java classes. These
managers are inturn executing sql queries. We need that the LSB and the simple
java class execute within the same transactional context. i.e if the manager throws
an exception, the LSB should roll back all the previous sql statements. The manager
doesnt do any transaction management (by retrieving UserTransaction) and simply
executes the sql calls.
Do you think that these calls will be covered by the same transaction context.
thanks for your time
anand

"anand raman" <[email protected]> wrote in message news:3f65cd27$[email protected]..
Question:
Will the transactional context be passed on from a LSB mediator to other java
components (simple java classes).
The LSB is delgating control to managers which are simple java classes. These
managers are inturn executing sql queries. We need that the LSB and the simple
java class execute within the same transactional context. i.e if the manager throws
an exception, the LSB should roll back all the previous sql statements. The manager
doesnt do any transaction management (by retrieving UserTransaction) and simply
executes the sql calls.
Do you think that these calls will be covered by the same transaction context.Yes, they will, provided a it' s a CMT LSLB and it has Required transaction
attribute.
Regards,
Slava Imeshev

How to disable a field in a standard transaction

Good day,
Can any one tell me , with an example of , how to disable (the field should not allow any input ) a parameter or a select option in a standard transaction.

Probably the only way to achieve this is by creating transaction variants:
In the SAP Reference IMG, you can create transaction variants. Choose Basis Components ® Application Personalization ® Tailoring of Application Transactions ® Configure Transaction-Related Display Values for Fields (Transaction SHD0). Transaction variants allow you to preset values for fields in a transaction, set field attributes, or hide entire screens.
To execute a transaction variant, you define a variant transaction using the Transaction Maintenance transaction (SE93).
Once you have entered a transaction code and short description, choose transaction type Transaction with variant (Variant transaction).
To define a variant, enter the name of the transaction and the name of the variant. You can then use the new transaction code to start the special variant of the transaction.
Steps :-
Transaction SHD0 - Create a variant for the required transaction bychanging the layout through hiding fields and screens.
Transaction SE93 - Create a variant transaction (e.g. for VA02 you canname it as ZA02). Next allocate the transaction variant to this varianttransaction.

Transaction Type for BAPI (fbo1)

Hi,
I am using FM 'BAPI_ACC_DOCUMENT_POST' to post the invoice,when i try to pass asset no bapi requires transaction type.can you any body help me out this
thanks,
gopal.

Hi
There is a table T856... See the data in SE16 transaction .The first field TRTYP various values.
Try the values, available in your system, one by one, from ...
100
105
120
125
130
140
145
150
170
200
205
220
230
240
245
250
270
275
280
500
505
520
540
560
570
580
900
910
920
930
Please reward suitable points.
Regards
- Atul

Required transaction

Similar Messages

Maybe you are looking for