Inbound Transaction

Hi,
What is the best practise to post IDoc's to SAP from MII. From my understanding A preferable alternative approach technically would be to call a BAPI instead of IDOC_INBOUND_ASYNCHRONOUS, because assigning the data to the BAPI structures would be a lot simpler than trying to populate data correctly in unformatted structures.However, having the data loaded into SAP using IDocs has its advantages, principally that you get the audit trail and error reprocessing functions of an IDoc.
Thanks,
Mukul

Hi Mukul,
This has come up several times in the last couple of years. Please seach back through this forum (Use IDOC_INBOUND_ASYNCHRONOUS as the search term) and set the timeframe to All. You should find the solution(s) you seek.
You may also want to take a look at Process Messages as the means of transport, or XI/PI from within the MII transaction.
Regards,
Mike

Similar Messages

WMS Putaway for inbound transactions

Hi,
I'm relatively new to WMS and was wondering the best method of performing an inbound receipt of goods and using a putaway rule/strategy to direct the goods to a particular subinventory/locator.
For example if the goods received are ammonia, the putaway rules would check the current locator capacities for the ammonia tanks and would also prevent co-mingling with other products in other tanks.
As far as I can see all inbound transactions (PO receipts form) and mobile inbound receipt transactions force the user to enter the destination details manually.
Many thanks in anticipation.

Hi
Sorry to be rude but the last answer is not quite correct.
You do create the TO but one of the point missing is that once the product has been located you must confirm the TO
Once this is done and you 'post goode receipt; in VL32N then that is it. There is no MIGO transcation required.
There are two ways to receive against an Inbound delivery
One is the one described and the other is to receive in IM first using MGO and this will create a TR in WM which then needs to be converted in to a TO etc etc
I hope that this helps

AGIS Inbound 'Transaction Status' changes to error on clicking Approve

Hi,
AGIS inbound 'transaction status' changes to error on clicking Approve or Apply button? how to find what is that error as I am not able to find any error message.
What are the causes for this error ?
I manage to generate the outbound transaction. When the recipient has received and approve, it shows an error under - Transaction Status and in the outbound side it shows Batch Status as Error.
Can some one help to to find out the way to fix it.
Thanks in Advance,
Thejas

Something might have gone wrong in the Workflow. Please check the metalink document 785167.1
Thanks,
John.

WE57 - for inbound transactions, outbound transactions, or both?

Hello,
Can anyone tell me if WE57 is used for inbound transactions only or is it used for both inbound & outboud? It seems in the documentation I have looked at, it states it is only for inbound. Why, then, when I try to create a new entry in WE57, does it ask for a direction (inbound or outbond)?
Any help would be great because I'm getting confused...thank you!!

The documentaiton below is very misleading then. Do you know why it only mentions WE57 for direct inbound?
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7ce043d711d1893e0000e8323c4f/frameset.htm

Setups for Directory where data files sit, in Inbound Transaction.

Hi,
My customer is implementing Inbound Po transaction using e-commerce gateway for Order Import in R12.
Could you let me know what setups i need to ask DBA's for creating inbound directory.
I just found one required setup online.
1) DBA's must define the UTL_FILE_DIR parameter in the INIT.ORA file.
Thanks.

I can see why no consensus was reached. I've now looked at that link, where some recommend a place in /usr, but the FSH info that I found says:
/usr is the second major section of the filesystem. /usr is shareable, read-only data
So that doesn't seem right.
Others recommend /var, but the FSH info says:
/var contains variable data files. This includes spool directories and files, administrative and logging data, and transient and temporary files.
Nope, not there either.
Final suggestion there is /home. The files don't need to belong to a particular user, as set forth previously, and the FHS helps with
/home is a fairly standard concept, but it is clearly a site-specific filesystem. The setup will differ from host to host. Therefore, no program should rely on this location.
For an OS that serves gazillions of files to as many users, it just strikes me as odd that there isn't a standard here. That being said, individuality is often a good thing.
Thank you for your suggestions, both of which make a lot of sense. I am leaning toward /home/share.

How to selectivly Dequeue inbound transactions comming to B2B

Hi
If I have an 850 Inbound and 810 Inbound from two different trading partners and there are two BPEL processes defined to handle these 2 transactions how to selectively dequeue the transactions to the correct BPEL Process.

Hello Kalyan,
It may be good idea for a quick call for me to explain it better. However just few tips
1. Please refer to the Configuring OracleASB2B section in the Integration with Oracle BPEL Process Manager chapter of the B2B user guide.
2. Document Routing ID is part of Document Type Parameters and is available for all Document Type in B2B.
3. Document Rounting ID in B2B needs to be set to appropriate Consumer Name of BPEL.
4. Please apply the latest patch.
5. Use the appropriate consumer name in BPEL.
Let us know.
Rgds,Ramesh

Movement types corrsponds to Inbound ,Outbound and Internal transaction

Hi,
Can anyone tell me the list of movement types corresponding to the Inbound,Outbound and for Internal Transaction.
for example: movement type 101 corresponds to Inbound transaction.
Thanks

Dear Bala,
This may help you.....
Below you will find a short description of the standard movement types. The cancellation movement type is the movement type + 1 (cancellation for 101 = 102).
101 Goods receipt for purchase order or order
If the purchase order or order has not been assigned to an account, a stock type (unrestricted-use stock, stock in quality inspection, blocked stock) can be entered during goods receipt.
If the purchase order or order has been assigned to an account, the goods receipt is not posted to the warehouse, but to consumption.
In the case of non-valuated materials, the goods receipt is posted to the warehouse, although the purchase order has not been assigned to an account.
Possible special stock indicators:
o     K Goods receipt for purchase order to consignment stock
o     O Goods receipt for purchase order to stock of material provided to vendor
o     E GR for purchase order or order to
o     sales order stock
o     Q GR for purchase order or order to
o     project stock.
Goods receipt for subcontract order : at goods receipt, the consumption of the components is posted at the same time (see movement type 543)
Goods receipt for
stock transport order : at goods receipt the transported quantity is posted in the receiving plant from stock in transit into unrestricted-use stock (or stock in quality inspection, blocked stock).
103 Goods receipt for purchase order into GR blocked stock
The GR blocked stock is not valuated.
You cannot receive goods into GR blocked stock for stock transport orders.
105 Release from GR blocked stock for purchase order
Movement type 105 has the same effects as 101.
121 Subsequent adjustment for subcontracting
This movement type cannot be entered manually.
With a subsequent adjustment for a subcontract order it is possible to correct the consumption of components. In this case, the material produced by the supplier is credited with the excess consumption / under-consumption. For this reason, if there is a subsequent adjustment, an item is generated for the produced material using movement movement type 121.
Movement type 121 does not have a reversal movement type.
122 Return delivery to supplier or to production
Using movement type 122, you can distinguish real return deliveries for a purchase order or order from cancellations (102).
In the standard version, you must enter a reason for the return delivery if you are using movement type 122. In this way, evaluations of return deliveries are possible.
The effects of movement type 122 correspond to a cancellation of movement type 101.
123 Reversal of return delivery
If you returned a goods receipt using movement type 122, you can reverse the return delivery using movement type 123.
Movement type 123 has the same effects as movement type 101.
124 Return delivery to vendor from GR blocked stock
Using movement type 124, you can return a goods receipt to GR blocked stock (103).
Movement type 124 has the same effects as movement type 104.
125 Return delivery from GR blocked stock - reversal
If you returned a goods receipt to GR blocked stock using movement type 124, you can reverse the return delivery using movement type 125.
Movement type 125 has the same effects as movement type 103.
131 Goods receipt for run schedule header
This movement cannot be entered manually. It is generated automatically at notification of goods receipt for a run schedule header.
Possible special stock indicators: E und Q
161 Return for purchase order
If a purchase order item is marked as a returns item, the returns to vendor are posted using movement type 161 when the goods receipt for purchase order is posted.
Movement type 161 has the same effects as movement type 122.
201 Goods receipt for a cost center
The goods can only be withdrawn from unrestricted-use stock.
Possible special stock indicators:
o     K: Goods withdrawal from
o     consignment stock
o     P: Goods withdrawal from pipeline
If you have withdrawals from consignment stock and from pipeline, payables to suppliers ensue.
221 Goods issue for a project
The goods can only be withdrawn from unrestricted-use stock.
Possible special stock indicators: K, Q
231 Goods issue for a customer order (without SD)
You use this movement type if you want to process the delivery without SD.
The goods can only be withdrawn from unrestricted-use stock.
Possible special stock indicators: E, K, Q
241 Goods issue for an asset
The goods can only be withdrawn from unrestricted-use stock.
Special stock indicator: K
251 Goods issue for sales (without customer order)
Use this movement type if you have not entered a customer order in SD. In the standard system, the movement is assigned to a cost center. kontiert.
The goods can only be withdrawn from unrestricted-use stock.
Possible special stock indicators: K
261 Goods issue for an order
This refers to all withdrawals for orders (for example, production order, maintenance order, except customer orders.
Possible special stock indicators: E, K, P, Q, W
The goods issue can be posted manually in Inventory Management or automatically when an order is confirmed or via an SD delivery.
281 Goods issue for a network
The goods can only be withdrawn from unrestricted-use stock.
Possible special stock indicators: E, K, P, Q
The goods issue can also be posted via an SD delivery.
291 Goods issue for any arbitrary account assignment
With this movement type, all account assignment fields are ready for input. You can assign the movement to an arbitrary account assignment object.
The goods can only be withdrawn from unrestricted-use stock.
Possible special stock indicators: E, K, P, Q
301 Transfer posting plant to plant in one step
The quantity is transferred from unrestricted-use stock in the issuing plant to unrestricted-use stock in the receiving plant.
Possible special stock indicators: O, V, W
303 Transfer posting plant to plant in two steps - removal from storage
The quantity is transferred from unrestricted-use stock of the issuing plant to stock in transfer in the receiving plant.
For technical reasons, you cannot carry out transfer postings from plant to plant in two steps for split-valuation materials.
Removal from storage can be posted via an SD delivery.
305 Transfer posting plant to plant in two steps - placement in storage
The quantity is posted from
stock in transfer to unrestricted-use stock in the receiving plant. The movement is not valuated.
You can enter the goods receipt with reference to the SD delivery.
309 Transfer posting material to material
The quantity is posted from unrestricted-use stock of the issuing material into unrestricted-use stock in the receiving material
Prerequisite: both materials have the same stockkeeping unit.
Possible special stock indicators: E, O, Q, V, W
311 Transfer posting storage location to storage location in one step
The quantity is transferred from unrestricted-use stock of the issuing storage location to unrestricted use in the receiving storage location.
Possible special stock indicators: E, K, M, Q
See also 321, 343, 349, 455 for other stock types.
313 Stock transfer storage location to storage location in two steps - removal from storage
The quantity is transferred from unrestricted-use stock of the issuing storage location to stock in transfer in the receiving storage location.
315 Transfer posting storage location to storage location in two steps - placement in storage
The quantity is transferred from the
stock in transfer to the unrestricted-use stock in the receiving storage location.
317 Creation of a structured material from constituent components (Retail)
A material split into its components using movement type 319 can be rejoined using movement type 317.
Movement type 317 has the same effect as a cancellation of movement type 319.
319 Split structured material into components (Retail)
You can enter the splitting of a structured material manually using movement type 319.
You can configure Customizing so that a structured material (for example, (z.B. set, prepack or display) is automatically split into its components at goods receipt. The system posts the split using movement type 319. In this process, the BOM header material is posted and each of the component stocks are increased. You can also use this function if you use the Warehouse Management System (WM).
Example:
A box of the structured material S contains 3 pieces of the component K1 and 4 pieces of the component K2. The following material document items result after the material is split at goods receipt:
     Qty      Unit      Material      Movement type
     1      box      S      101 +
     1      box      S      319 -
     4      piece      K1      319 +
     5      piece      K2      319 +
321 Transfer posting stock in quality inspection - unrestricted-use stock
The quantity is transferred from stock in quality inspection into unrestricted-use stock. Here it is possible to post the quantity to another storage location.
This movement type is not possible for QM-managed materials since the transfer posting for these materials takes place using the usage decision.
Possible special stock indicators: E, K, O, Q, V, W
323 Transfer posting storage location to storage location - stock in quality inspection
The quantity is transferred from stock in quality inspection in the issuing storage location into stock in quality inspection in the receiving storage location.
Mögliche Sonderbestandskennzeichen: E, K, Q
325 Transfer posting storage location to storage location - blocked stock
The quantity is transferred from blocked stock in the issuing storage location into blocked stock in the receiving storage location.
Possible special stock indicators: E, K, Q
331 Withdrawal of sample from stock in quality inspection
333 Withdrawal of sample from unrestricted-use stock
335 Withdrawal of sample from blocked stock
The sample is destructive, that is, the withdrawal has the same effects as scrapping.
Possible special stock indicators: E, K, Q, V, W
341 Change in status of a batch (available to not available)
This goods movement is automatically created when there is a change in the status of a batch and it is also used to transfer the unrestricted-use stock into restricted-use stock.
Possible special stock indicators: E, K, M, O, Q, V, W
343 Transfer posting blocked stock - unrestricted-use stock
349 Transfer posting blocked stock - stock in quality inspection
The quantity is transferred from blocked stock to unrestricted-use stock (343) or stock in quality inspection (349).
Here it is possible to transfer the quantity to another storage location.
Possible special stock indicators: E, K, Q
351 Goods issue for a stock transport order (without SD)
The quantity is transferred from unrestricted-use stock in the issuing plant to stock in transit in the receiving plant.
Movement type 351 is only used if the goods issue is posted without an SD delivery. A goods issue for a stock transport order with SD delivery is posted using movement type 641 or 643.
The transfer posting is also possible for materials valuated separately.
The goods issue for a stock transport order takes place using movement type 101.
Possible special stock indicators: E, Q
For special stock indicators E and Q and for purchase orders assigned to an account, ensure that the quantity is not posted to the stock in transit in the receiving plant.
401 Transfer of sales order stock into company's own stock
(no longer available as of Release 4.0C)
The quantity is transferred from unrestricted-use sales order stock (non-valuated) into unrestricted-use storage location stock (valuated). For this movement, a special stock indicator is not required.
It is possible to change the material number using this movement - if the material is managed in the company's own stock under a different material number (for example, for materials that can be configured).
403 Transfer of consignment stock to company's own stock
(no longer available as of Release 4.0C)
The quantity is transferred from unrestricted-use consignment stock into unrestricted-use storage location stock and thus taken into the valuated stock. This results in a payable for vendors. For this movement, a special stock indicator is not required.
405 Transfer of project stock to company's own stock
(no longer available as of Release 4.0C)
The quantity is transferred from unrestricted-use project stock to unrestricted-use storage location stock. A special stock indicator is not required for this movement.
411 Transfer of special stocks E, K, and Q to company's own stock
The quantity is transferred from unrestricted-use special stock E ( sales order stock ), unrestricted-use special stock K ( consignment stock) and unrestricted-use special stock Q ( project_stock ) to unrestricted-use storage location stock. The corresponding special stock indicator is required for this movement.
If you do not use the special stock indicator, the system uses this movement type and movement type 311.
For sales order stock, you can change the material number for this movement if you manage the material in your company's own stock under a different material number (for example, for configurable materials).
Consignment stock is transferred to valuated stock, thus resulting in a vendor liability.
441 Transfer posting non-tied to tied empties
Part of the stock of an "empties" material assigned to a full product is managed in the stock type "tied empties".
Empties stock not assigned to a full product forms part of the stock type "unrestricted-use".
Using movement type 441, you can make a transfer posting for an empties material from the stock type "unrestricted-use" to the stock type "tied empties". Movement type 442 reverses this transaction.
Example:
The full product "beer" has a stock of 15 cases. Part of the empties components "bottle" and "case" is tied empties stock.
     Material      unrestricted-use      tied empties
     Beer      15
     Bottle      240      360
     case      10      15
451 Returns from customers (without SD)
Using movement type 451, you post customer returns without an SD returns delivery into blocked stock returns . The blocked stock returns are not valuated.
No special stock indicator possible.
See also 453, 651, 653
453 Transfer posting blocked stock returns to unrestricted-use stock
457 Transfer posting blocked stock returns to quality inspection stock
459 Transfer posting blocked stock returns to blocked stock
The quantity is transferred from blocked stock returns to unrestricted-use stock (453), quality inspection stock (457) or blocked stock (459) and thereby transferred to valuated stock.
With this movement you can transfer the quantity to another storage location at the same time.
455 Transfer posting storage location to storage location - blocked stock returns
The quantity is transferred from blocked stock returns of the issuing storage location to blocked stock returns of the receiving storage location.
501 Goods receipt without purchase order - unrestricted-use stock
503 Goods receipt without purchase order - stock in qual.inspection
505 Goods receipt without purchase order - blocked stock
These movement types are used for deliveries from vendors that are not based on a purchase order. Invoice verification is not possible for these goods receipts.
Mögliche Sonderbestandskennzeichen: E, K, M, Q
Bei einem Wareneingang zur Bestellung (101) kann der Zugang von
Mehrwegtransportverpackung als zusätzliche Position mit 501 und Sonderbestandskennzeichen M erfaßt werden.
511 Free-of-charge delivery from vendor
The quantity is posted to unrestricted-use stock. If there is a material with moving average price, the moving average price is reduced accordingly.
521 Goods receipt without order - unrestricted-use stock
523 Goods receipt without order - stock in quality inspection
525 Goods receipt without order - blocked stock
The movement types are used for deliveries from production that are not based on a delivery.
Possible special stock indicators: E, Q
531 Goods receipt from by-product from the order
The goods receipt of a by-product usually refers to an order, but it can be entered without a reference.
If a component is entered with a negative quantity in the order, a reservation item is created with 531 (instead of 261). The receipt of a by-product can be entered when the component for the order is withdrawn from stock or it can be entered as another type of goods receipt.
Possible special stock indicator: E, Q
See also: 545 and 581
541 Transfer posting unrestricted-use stock - stock of material provided to vendor
WIth the movement type you provide the subcontractor with the components required for subcontract orders . The quantity is posted into unrestricted-use stock of material provided to vendor.
If there is a goods receipt for a subcontract order (101), the consumption of components is posted from this stock.
Special stock indicator cannot be used.
The transfer posting can be posted via an SD delivery.
543 Consumption from stock of material provided to vendor
This movement cannot be entered manually.
The consumption of components for a subcontract order is posted using goods receipt for purchase order (101). It can be corrected by means of a subsequent adjustment.
Possible special stock indicators: E, Q.
For the special stock indicators E and Q, you must ensure that the quantity is not removed from the stock of material provided to vendor, but from the unrestricted-use sales order or project stock.
545 Goods receipt from by-product from subcontracting
If a component is entered with a negative quantity for the subcontract order, the receipt of the by-product is posted during goods receipt for purchase order or during the subsequent adjustment.
Possible special stock indicators: E, Q
For special stock indicators E and Q, you must ensure that the quantity is not posted to the stock of material provided to vendor, but to the unrestricted-use sales order or project stock.
551 Scrapping from unrestricted-use stock
553 Scrapping from stock in quality inspection
555 Scrapping from blocked stock
Possible special stock indicators: E, K, Q
561 Initial entry of stock - unrestricted-use stock
563 Initial entry of stock - quality inspection
564 Initial entry of stock - blocked stock
During initial entry of stock balances, you enter the physical warehouse stock frigures or the book inventory from your old system into the SAP System for productive operation. This data entry usually takes place by means of batch input.
Possible special stock indicators: E, K, M, O, Q, V, W (565: only E, K, Q)
571 Goods receipt for assembly order to unrestricted-use
573 Goods receipt for assembly order to quality inspection
575 Goods receipt for assembly order to blocked stock
This movement cannot be entered in Inventory Management, but only in repetitive manufacturing using the function "Goods receipt for sales order".
Possible special stock indicators: E, K, Q
581 Goods receipt of a by-product from the network
The goods receipt of a by-product usually refers to a network , but can be entered without reference.
If a component is entered with a negative quantity in the network, a reservation is created with 581 (instead of 261). The receipt of a by-product can be entered during the withdrawal for the network or as another type of goods receipt.
Possible special stock indicators: E, Q
601 Goods issue for delivery (SD)
This movement cannot be entered manually. It is created automatically in SD using the function "Goods issue for delivery".
The quantity is taken from unrestricted-use stock.
Possible special stock indicators: E, K, Q
621 Transfer posting unrestricted-use - returnable packaging (SD)
This movement is generated by SD.
The quantity is transferred from unrestricted-use stock to the returnable packaging stock at customer .
623 Goods issue from returnable packaging stock at customer(SD)
This movement is generated by SD.
This quantity is withdrawn from unrestricted-use returnable packaging stock at the customer.
631 Transfer posting unrestricted use - customer consignment stock (SD)
This movement is generated by SD.
The quantity is transferred from unrestricted-use stock to consignment stock at customer.
633 Goods issue from customer consignment (SD)
This movement is generated by SD.
The quantity is withdrawn from unrestricted-use consignment stock at the customer.
641 Goods issue for a stock transport order (SD)
This movement is generated by SD.
The quantity is transferred using an SD delivery from unrestricted-use stock of the issuing plant to stock in transit of the receiving plant.
The goods receipt for the
stock transport order takes place using movement type 101 and can, if required, refer to the purchase order or to the delivery.
Possible special stock indicators: E, Q
For the special stock indicators E and Q and for purchase orders assigned to an account, you must ensure that the quantity is not posted to the stock in transit of the receiving plant.
See also: 351, 643
643 Goods issue for a cross-company stock transport order (SD)
This movement is generated by SD.
It is used only for cross-company stock transport orders with SD billing and invoice. The quantity is withdrawn from the unrestricted-use stock of the issuing plant. No stock in transit is created here. In the second step, the goods receipt must be entered.
Siehe auch: 351, 641
645 Goods issue for a cross-company stock transport order in one step
(SD)
This movement is generated by SD.
Unlike movement type 643, when a goods issue is posted using movement type 645, a goods receipt line is generated automatically.
647 Goods issue for a stock transport order in one step (SD)
This movement is generated by SD.
Unlike movement type 641, when a goods issue is posted using movement type 647, a goods receipt line (101) is generated automatically.
651 Returns from customer (SD)
This movement is generated by SD.
Using movement type 651, you post returns from a customer with the SD returns delivery to blocked stock returns . The blocked stock returns are not valuated.
Special stock indicators not possible.
See also: 451, 453, 653
653 Returns from customer (SD) to unrestricted-use stock
655 Returns from customer (SD) to stock in quality inspection
657 Returns from customer (SD) to blocked stock
These movements are generated by SD.
With these movement types you post returns from the customer with SD returns delivery directly to the valuated stock.
Possible special stock indicator: E
See also: 451, 453, 651
661 Returns to vendor via SD delivery
As with movement type 502, a return delivery to the vendor is entered without reference to the purchase order, but the goods issue is posted via an SD delivery.
671 Returns for stock transport order via SD delivery
If a purchase order item is marked as a returns item, when a goods receipt for a stock transport order (101) is posted, the return is posted to stock in transit using movement type 161. When the return arrives, the issuing plant posts the goods receipt for the return using movement type 671. Movement type 671 (like movement types 352 and 642) reduces the receiving plant's stock in transit and increases the the issuing plant's unrestricted-use stock.
701 through 708: Inventory differences in MM
These movements are generated automatically during inventory difference posting in Inventory Management.
711 through 718: Inventory differences in MM-WM
These movements are generated when you post the inventory differences from Warehouse Management to Inventory Management.
721 - Sales value receipt - not affecting margins (Retail)
The movement is generated automatically when the sales price of a value-only material is changed (total sales price revaluation on the posting date).
731 - Sales value receipt - affecting margins (Retail)
The movement is generated automatically when the sales price of a value-only material is changed (partial sales price revaluation on the posting date).
Regards
Ravi

Issue in Setting up Inbound and Outbound 997 in B2B

Hello All-
Please find the background and issue details.
Background
=======
1. We use a common business action (Doc Type:997 and Doc Type Revision: 4010) to send Outbound 997 to the Trading Partners for the corresponding inbound documents from them. This common Business Action is used across all Trading Partners set up in the system to send Outbound 997. We attach this business action to the agreement for a particular Inbound Transaction Agrmnt
2. As per new requirement, we have to enable Inbound 997 which is also Doc Type : 997 and Doc Type Revision as 4010. However, as mentioned above, since there is already a Business Action with doc type 997 and doc type revision 4010 combination, B2B did not allow us to setup the common inbound 997 business action
3. As a workaround we modified the Doc Type Revision of the Common Outbound 997 Business Action to some random number and redeployed all the configurations that were using the Outbound 997 Business Action. We retained the Doc Type Revision as 4010 for the Inbound 997 Business Action.
Issue Details
=======
1. After modifying the Outbound Business Action, as mentioned above, B2B is failing to identify the Outbound 997 Business Action and hence not able to generate the Outbound 997 for a particular inbound document.
If anybody has faced similar issue, I would really appreciate if you can provide me pointers to resolve this issue and also let me know if we are doing the set-ups correctly.
Please let me know if you need any additional information from my side.
Thanks,
Dibya

Hi Dibya,
In case of outbound EDI, document type and document type revision is used to identify a transaction set. Check whether you are receiving these two values correct. On the basis of transaction set and trading partner, it will identify the agreement and then find the particular business action in that agreement.
Can you please mention that till what step your B2B is able to process the outbound EDI document?
Thanks & Regards,
Anuj

SO via inbound EDI. partner problem LIFNR - PARTN

Hi,
Working on PO -> SO interface. Question on populating VOE4 (EDPAR).
in the inbound IDOC I have this segment:
E1EDKA1:
PARVW: AG
PARTN: external customer number (in my case it is purchasing organisation)
LIFNR: 'blank'
In forums it is told that segment LIFNR should be populated by external customer number.
What is the difference between PARVW and LIFNR? Does VOE4 look at PARTN for substitution?
in my case seems that it ignores PARTN at all..
Thanks,
Artashes

I think what you need is the following.
On the EDIDC record, field SNDPRN, you need to have the Sold To customer number mapped. You'll also need to have the SoldTo setup in WE20 with a partner profile.
You can send in an Order to SAP with a Logical System in the above field but you then have to have the PARTN fields filled in with the correct Sold To Ship To. Which you typically would not have.
On the KA1 segments, you'll need two KA1 segments, one for the Sold To and the Other for the Ship To. Since you already would know the Sold To since you put it in the EDIDC record, just fill it in the PARTN field, unless your partner wants their store number back. Personally I would set it up this way with the external store number.
So you'll want a KA1 record with the AG qualifier for the Sold To and the LIFNR field filled in with the partners external number for the Sold To. This could be the Duns number or N1/04 code.
On the second KA1 for the ship to, set the qualifier to WE for Ship To and then fill in the LIFNR with the external store number.
You'll now need entries in VOE4 for each KA1. Customer would be the same as the Customer in the EDIDC record, field SNDPRN. external function is either SP or SH. External Number is the external number, either the DUNS number for the Sold To (Most likely) or the N1/04 code for the ship to. Int No is the Internal customer number for the Sold To and Ship To.
Sold To 55555
Customer Sender ID/Dunning # 123456789
External Ship To Store # 321
WE20 setup for Sold To 55555
VOE4 setup for 55555    SP    SOLD TO   123456789 55555
VOE4 setup for 55555    SH    SHIP TO     321              55555
I think what SAP Messed up on is the fact that we should not have an external cross reference or hard coding mechanism to populat the SNDPRN with a customer number for inbound transactions in order for the EDPAR table to work correctly. You can have a logical system at the EDIDC level but would need to populate the correct Sold To and Ship To on the KA1 segments. When using the LIFNR fields, SAP Uses the SNDPRN, External Partner Number and Partner Function on the KA1 record to determine the Internal Customer Number.
If anyone else has an opinion please let me know.   I would love a way to be able to cross reference the Dunning Number for a partner to a Sold To within SAP and allow for the LIFNR fields to be used for the Ship To's.

Error in inbound processing: EDI message - XML Gateway

Hello!
I've setup a DELFOR transaction in B2B and modified XML Gateway settings for internal delivery channel in order to send the message to EBS, but I'm getting weird errors in b2b.log. (XML Gateway in EBS is not setup yet, but it should't be an issue since incoming errors are handled in EBS, and I would just see an inbound transaction with processing errors in Transaction Monitor.)
In the beginning of b2b.log I see this:
2009.07.07 at 15:26:31:897: B2BStarter thread: BusinessLogicLayer - (DEBUG) Push Stack: queryInternalDeliveryChannel
2009.07.07 at 15:26:31:897: B2BStarter thread: BusinessLogicLayer - (DEBUG) Pop Stack: queryInternalDeliveryChannel
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound initialize
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 Obtaining inbound connection...
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound connect string: jdbc:oracle:thin:@server64.xa.si:1521:test2
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound username: apps
2009.07.07 at 15:26:32:522: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:32 CEST 2009 inbound initialize exit
2009.07.07 at 15:26:32:522: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Enter
2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Exit
2009.07.07 at 15:26:32:538: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run Thread start
2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Exit
2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) B2BStarter - B2B initialized
After I copy the edi file to the incoming directory B2B starts processing the file:
2009.07.07 at 15:30:01:878: Thread-10: B2B - (DEBUG)
Protocol = File
Version = 1.0
Transport Header
filename:00003442_23.CMS
filesize:12345
file_ext:CMS
fullpath:C:\xa_endpoint\00003442_23.CMS
timestamp:2009-07-06T16:14:29.393+01:00
As I see in the log: B2B finds the trading partner and agreement and all looks fine. But later comes this:
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination Enter
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to destination. protocol is XMLGateway Queues
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to XMLGW
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 Converting B2B message to ECX message..
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 Inbound - B2BtoECX - Enter
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 B2B Message -
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : COLLABORATION_NAME : null
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : ACTION_NAME : DELFOR
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DOCUMENT_TYPE : DELFOR
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DOCUMENT_TYPE_REVISION : D97A
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : SOURCE_NAME : tpartner
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DESTINATION_NAME : Xa d.d.
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : PAYLOAD : UNB+UNOA.............. edi message continues here
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) : PAYLOAD : <?xml version="1.0" ?><Transaction-DELFOR............... xml continues here
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 ECX Message -
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry Could not deliver the message; exception message is null
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry No application side retry
2009.07.07 at 15:30:06:081: Thread-9: B2B - (ERROR) Error -: AIP-50903: Message "0A14011912255682A58000003257C600-1" retry count is zero
     at oracle.tip.adapter.b2b.msgproc.MessageHandler.handleAppMessageRetry(MessageHandler.java:394)
     at oracle.tip.adapter.b2b.msgproc.MessageHandler.deliverMessageToDestination(MessageHandler.java:344)
     at oracle.tip.adapter.b2b.msgproc.Request.putMsg(Request.java:657)
     at oracle.tip.adapter.b2b.msgproc.Request.continueRequest(Request.java:481)
     at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:410)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:2062)
     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
     at java.lang.Thread.run(Thread.java:534)
Last message repeats once more and then:
2009.07.07 at 15:30:06:081: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.07.07 at 15:30:06:081: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: updateBusinessMessage
2009.07.07 at 15:30:06:096: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: updateBusinessMessage
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateMsgError(3 params) Exit
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Enter
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Transaction.commit()
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Leave
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination Exit
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Exit
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: processIncomingMessage setting seq numbers
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Call Incoming Request Processor
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Enter
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest TransportBindings created
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Create a Message Table Row for Request message with message state Continue Processing
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: queryExchangeProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: queryExchangeProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: queryDocumentProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: queryDocumentProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (ERROR) Error -: AIP-13115: Not in an active transaction
     at oracle.tip.repos.core.persistency.BaseObject.prologue(BaseObject.java:1408)
     at oracle.tip.repos.core.persistency.BaseObject.createObject(BaseObject.java:913)
     at oracle.tip.model.instance.DataStorage.create(DataStorage.java:794)
     at oracle.tip.adapter.b2b.message.MessageStorage.create(MessageStorage.java:145)
     at oracle.tip.adapter.b2b.msgproc.DbAccess.insertMsgTblRow(DbAccess.java:953)
     at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:397)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:2062)
     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
     at java.lang.Thread.run(Thread.java:534)
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) setRuntimeActiveandQuiescing()
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage General Exception ERROR
Error repeats a few times.
Wire message stays in Processing status, Business message is errored and an exception message is created in ip_in_queue.
Both remote and host delivery channels have retry set to 1. Agreement was re-deployed + all B2B restared, but the problem remained.
Could anyone help with this? What could be wrong?
Thanks in advance.
Kind regards,
Wanda
PS. I've checked all threads that might have anything to do with this, but found nothing useful.

Hi Anuj,
thanks for taking the time to examine the file.
Answers to your questions:
1. Yes, this is the 1st time for B2B, but the EBS I'm trying to connect to is up and running for approx. 2 years (it's a test instance).
2. Patching was done by the customer's sysadmin, so I don't really have an overview on what and how he did. Result of opatch:
Installed Patch List:
=====================
1) Patch 8298731 applied on Sat Jun 13 09:23:42 CEST 2009
2) Patch 5907304 applied on Thu Jul 17 14:26:55 CEST 2008
3. In theory the sysadmin should have run it, but how could I double-check this?
I know he had problems while applying patch 8298731, but he said it was solved later. (Customer is using windows os, which is making a lot of troubles otherwise.)
Regarding IDC log there is no success. I've restared B2B at least 5 times plus once the database, but still nothing. In tip.properties:
oracle.tip.adapter.b2b.transportTrace = C:\APPS\OAS\ip\log/transport.trc
also I tried the following values:
C:\\APPS\\OAS\\ip\\log/transport.trc (since there is a similar entry: oracle.tip.LogDirectory = C:\\APPS\\OAS\\ip\\log)
C:\\\\\\\\\\\\\\\\APPS\\\\\\\\\\\\\\\\OAS\\\\\\\\\\\\\\\\ip\\\\\\\\\\\\\\\\log/transport.trc (this was commented before; maybe it comes from some default)
true (I had no other idea)
Result is the same for all the cases: b2b_idc_transport.log file is 0 bytes, but b2b_dc_transport.log has initial data+writes log when processing.
If I remove or comment the above line from tip.properties, then no transport log files are created.
I've updated the agreement to have B2B inbound for the internal delivery channel, re-deployed it and it worked fine -> transaction(s) appeared in IP_IN_QUEUE.
Changing it back to XML Gateway (and re-deploying) causes all original problems.
Regards,
Wanda

What is the b2b setup for identifying TP names from file name in Inbound tx

Hi,
I am using B2B 11g version and documents of type ANSI-X12. I am working for Inbound Transaction and using Generic File protocol in Listening channel.
File format is : %FROM_PARTY%_%TO_PARTY%_%DOCTYPE_NAME%_%DOCTYPE_REVISION%.dat
How can i make B2B to identify Trading partner names from the file name once the remote trading partner put the file in the specified path with the specified format "%FROM_PARTY%_%TO_PARTY%_%DOCTYPE_NAME%_%DOCTYPE_REVISION%.dat" mentioned in the delivery channel.
Now B2B is identifying Trading partner names from the Interchange Sender ID(ISA06) and Interchange Reciever ID(ISA08) of the ISA Segment. Please help me , how to make B2B to identify the trading partner names from the file name instead of from identifiers coming in ISA Segment.
Thanks,
Sridhar Rachumallu

Hi Anuj,
1)Now i am giving the file name for inbound documents in the format of "%FROM_PARTY%_<UniqueNumber/Timestamp>.dat" . But still B2B Identifying the TPNames at runtime from the ISA Segment elements ISA06 & ISA08 element values. I want to make B2B to identify the TPNames at run time from the file name instead of from ISA Segments.
Please tell me how can i do these?
2) I am giving exact Remote Trading partner Default Identifier Type 'NAME' value for "%FROM_PARTY% in the file format and i want B2B to identify the TP name at runtime based on the value of "%FROM_PARTY%" . If the value of "%FROM_PARTY%"is matching with any one of the Trading partner Default Identifier Type 'NAME' value than it should go for furthur else B2B should through error as " the TP name unable to found".
3) Please tell me how B2B Identify trading partners at runtime in the business case given below
- Inbound Transaction from remote TP to Host TP
- Document protocol is 'ANSI-X12'
- Listening channel protocol is 'Generic File'
This is very urgent.. Please give the reply As soon as possible.
Thanks,
Sridhar.rachumallu
Edited by: [email protected] on Jun 9, 2010 12:45 AM
Edited by: [email protected] on Jun 9, 2010 1:01 AM

Issue with EDI_X12_850 Inbound

Hi,
I am trying to perform Inbound transaction [ EDI_X12_4010_850] in Oracle B2B. In this case XYZ and ABC are the host and remote trading partners respectively.
On the Administration--> Listening Channel page, I have created a listening channel with name "ABC" and placed the EDI file "ABC_4010_850.dat" in the channel.
Also , created a SOA composite having Oracle B2B Receive [ 850 ] as an Inbound process and succesfully deployed the same. Once the file is picked from the channel ABC an xml file [ xml file having data as that of EDI ]
is getting generated in the host channel location. But the SOA composite is not getting trgiggered.
Any suggestions please
Thanks
Surya

Hi ,
Thanks for your reply.
SOA composite is not getting triggered, I do not see any instance for this composite [ composite which has Oracle B2B inbound [ 850] ]
In the Application Message i could see the state of the message as "COMPLETE" but it does not have any information of the composite [ as the composite did not get triggered ]
Could you please let me know the workaround for this issue.
Thanks
Surya

As2 Inbound message processing

Hi
Am trying process custom xml using AS2 protocol but facing error while document Identifaction.It is throwing error as B2B-50547 Agreement not found for trading partners: FromTP null, ToTP MyCompany
Here is what I have done.
Created Custom document definition using B2B console Admin tab.Also selected doc tpe as XML and under xml tab below provided Xpath expression with appropriate value for document identification.
Xpath Identification Expression : //*[local-name()='type']/text() =======Identification Value as "XYZ"
Created Host and remote trading partner and deployed Agreement.Remote TP will post xml message to Host TP(will write to a file using File channel) which is Inbound transaction using default http listener(/b2b/httpReceiver).
Sample xml posted to b2b http listener
<EmployeeMsg>
<EmployeeHeader>
   <type>XYZ</type>
   <sender>Oracle</sender>
   <receiver>MyCompany</receiver>
</EmployeeHeader>
<Employee>
   <EmpId>123</EmpId>
   <fname>abc</fname>
   <lname>def</lname>
</Employee>
</EmployeeMsg>
Please help me to resolve above.
Also I wanted to convert this custom xml to EDI 4010 document to send to another trading partner.Please let me know how to translte to EDI document.Should it be something like below or can I do it without using composite?
RemoteTP1---------cusom xml over http listenr------------------->HostTP-----SOA Composite(to translate custom xml to EDI xml)----->HostTP----------------->Remote TP2(EDI format)

Hi Ismail,
I was initiating transaction by posting xml message over default http receiver(http://host:port/b2b/httpReceiver).I am not really sure how to pass AS2-From while posting message.
Here is wire message
Id
0A60435013F87742041000004F61E552
Message Id
0A60435013F87742041000004F61E552
Business Message
0A60435013F877420C5000004F61E559
Packed Message
Packed Message
Payload
Payload
Protocol Message Id
0A60435013F87742076000004F61E556
Refer To Protocol Message Id
Protocol Collaboration Id
Protocol Transport Binding
User-Agent=Apache-HttpClient/4.2.3 (java 1.5) Host=xxxxapp01:8001 Connection=keep-alive Content-Type=application/x-www-form-urlencoded Content-Length=385 MSG_RECEIVED_TIME=Thu Jun 27 17:05:02 EDT 2013
Message Digest
Message Digest
Digest Algorithm
Transport Protocol
HTTP
Transport Protocol Version
1.1
Url
http://xxxx:8001/b2b/httpReceiver
security
Transport Headers
User-Agent=Apache-HttpClient/4.2.3 (java 1.5) Host=xxxsoaapp01:8001 Connection=keep-alive Content-Type=application/x-www-form-urlencoded Content-Length=385 MSG_RECEIVED_TIME=Thu Jun 27 17:05:02 EDT 2013
certificates
certificates
State
ERROR
Error Code
Error Description
Error Text
exchangeRetryInterval
exchangeRemainingRetry
Message Size
385

B2B Inbound Error : Need Clarification

Hi All,
I would like to illustrate a particular use case for B2B Inbound Errors and if there is any workaround available to get over the problem. We are using B2B version 10.1.2
Use Case Details</strong1. Consider the scenario wherein we have a Inbound EDI File which has 100 transactions in it. B2B reads the file and automatically debatches into individual transactions and processes them separately.
2. Out of the 100 transactions in the input file, if say 5 transactions are error transactions, we have observed that all the 100 transactions error out in B2B.
3. The 95 correct transactions fail with the error "General Validation Error" and the 5 error transactions have the exact error details in the B2B Message Reports.
4. Ideally, B2B should error out only the 5 error transactions and process rest of the 95 transactions without allowing them to fail with "General Validation Error".
I am sure that most of us must have faced this error. Could someone please let me know the folllowing:
1. Is there any setting in B2B by which we can enable it to error out only the transactions which have valid errors in a single file
2. Is there any other workaround that we can take to avoid this issue.
The reason we need to have a solution for this is because in our Production B2B environment we receive inbound files from Trading Partners which have hundreds of transactions in each file.
If, even a single transaction has error, then the whole file errors out and it is quite cumbersome to browse through the B2B Message Reports to get the exact error transaction because all the correct transactions would failed with error "General Validation Error".
Please let me know the inputs.
Thanks,
Dibya

Hi Ramesh,
Thanks for the clarification and information. We have already set the parameter OneErrorAllError = true and my understanding was that if we set this parameter to TRUE, it means that if one transaction in the OUTBOUND batch errors out then the whole batch will error out.
I was not aware that it also holds true for INBOUND. Is there any other way that we can set this parameter based on direction (INBOUND or OUTBOUND).
We would like to have this parameter set for OUTBOUND and disabled for INBOUND Transactions.
Please let me know. Thanks Again.
Regards,
Dibya

How to define a transaction queue in xmlgateway setup?

Hi folks:
I have made a sample in XMLgateway successfully. But that is using the OTA way, which I send the request use the Oracle Transport Agent with this link:http://[hostname]:[port]/webservices/ECXOTAInbound, and I can see the status in Transaction Monitor is successful. And From Oracle DB, I can see the message is enqueued the ecx_inqueue table(Inbound Message Queue) first, and then the workflow BES enqueues the message to the ecx_in_oag_q_table(inbound transaction queue) for XML gateway to process.
And my question is: When I try to send the message rather by axis client than by the link http://[hostname]:[port]/webservices/ECXOTAInbound, there is no record for this message in Transaction Monitor. And from Oracle DB, I can see the message is enqueued the wf_ws_jms_in table(Inbound Message Queue) first, and then the message is not enqueued into ecx_in_oag_q_table(Inbound transaction queue). But a error message is insert into ecx_inbound_logs.
So,What I want to ask for help are following:
1.How can I define the transaction queue for trading partner's transaction?
2.Is there another inbound transaction queue I can use for wf_ws_jms_in(Inbound Message Queue)?
3.Is this transaction queue(ecx_in_oag_q_table) only receive the message from ecx_inqueue table(Inbound Message Queue)? If yes, what's the transaction queue receive the message from wf_ws_jms_in table(Inbound Message Queue), and How can I assign this transaction queue to my JMS and web service request trading partner?
I really appreciate if anyone can help me to make such thing clear. Thanks very much.I'm always waitting...

i have a program in production system if i type the request and execute its sends a mail to my admin saying to transport the request to production system.....thats y??????
just tell me ur idea.............

Inbound Transaction

Similar Messages

Maybe you are looking for