F9N7- IDOC FINSTA not created

Hi,
We are using IHC for inter company cash within group. Normally an IHC process chain runs overnight and we have no issue. However, today we manually ran F9N7, as overnight job did not pick up some payment orders and did not create bank statement.
On running F9N7 we were able to create bank statement(I see entry in table BKKM1) however system did not create IDOC type FINSTA.
How do we create idoc type FINSTA for both sending and receiving companies(bank statements) as i am unable to rerun F9N7 as bank statement is already created.
Kindly advise
Umang

Have you resolved the issue?

Similar Messages

Idocs were not created for AP Intercompany Invoice... ???

Hi Gurus
We are dealing with Europe subsidiaries. X and Y are the comp codes. For the company code X , there are no I docs created for the AP Inter Company invoice from the Company code Y.
Program RSNAST00 and transaction BD87 are used in all other European subsidiaries for the automatic posting of the Inter company AP invoices for product.
By using the above information how can i generate the I docs in automatic posting of the inter company AP invoices.
Can any body guide me with the program changes or transaction next steps.. back ground of the issue with a solution ?
Your response is highly appreciated and awarded.
Thanks in Advance
Meenakshi

Any response in this regard.. ?

IDOC not created in R/3

Hi,
I am sending IDOC from XI to R/3 using IDOC Adapter.
When I send around 2000 documents(2000 idoc are created in R/3)it works fine and I can see Idoc created in WE02.
But When I send more then 6000 documents,IDOCS are not created in R/3.But I can see in idx5 in XI 6000 outbound idocs.
Thanks in advance.
Rekha.

Have you checked whether the tRFC queue is full and creating with time delay ?
Try to increase remote user login parameter in the instance profile.
regards
Shravan

** File to IDoc scenario - IDoc not created in target system

Hi friends,
We are doing File to IDoc scenario. We made required setting in both application as well as XI system. While test the scenario, the file is picked up and successfully processed in SXMB_MONI, but the inbound IDoc is not created in target system. What could be the problem?
We are using DEBMAS message type DEBMAS06 IDoc type. We checked the following.
1) SM59 - Connections are OK both application and XI system
2) IDX1 - In XI System, we have assigned SAP<R/3> port.
3) IDX2 - IDoc is imported.
4) In ID - Sender File - Business Service - Adapter-Specific Identifier - Logical System name is given.
5) In application system. - Partner Profile maintained correctly.
6) SM58 - There is no error.
So, what could be the reason ?
Kindly reply, friends,
Thanking you.
Kind Regards,
Jeg P.

Hi,
Check all the steps ..
File to IDOC
Do these configurations in R/3 and in XI...
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
Thanks,
Satya

IDOCs not created for Payment method "P" and "B"

Dear Experts,
I have executed the Automatic Payment program for three payment methods (P,V and B - Foreign Currency) in one Run ID. Payment run was successful but it has created IDOCs for the documents / Vendors attached with payment method "V" but IDOCs were not created for the payment methods "P" and "B". I have checked the configuration relating to payment methods and those were assigned with Form details and the maximum amount is also defined in the payment methods.
Can any one suggest me where I had made the mistake / where I need to check the configuration settings.
Thanks a lot.
Regards,
Ramnath.

Hi Surya,
Please find below error log created while executing the Payment run for the issue.
Step 002 started (program SAPFPAYM_SCHEDULE, variant &0000000116195, user ID V-PIZHA)
Step 003 started (program RFFOEDI1, variant &0000003957078, user ID V-PIZHA)
Maintain an output device in your user master record
Job cancelled
Thanks and Regards,
Ramnath,
SAP FIMM Team

Outbound ORDRSP IDOC not created while processing using ALE_PROCESSING .

HI ALL,
i have done all the requiured config for o/b message control for ORDRSP idoc along with config in sale for dist.. model and assigning msg type to model etc and when i save my PO i can see the o/p being proposed but when i process that with A as medium, it is incorectly processed and no ordrsp idoc is created.i am using std idoc_output_ordrsp FM, when i debug the code the see an error in ALE_PROCESSING IN the perform new_dyn_perform
can anyone pls tell me why the idoc is not created.
thanks,

Hi eswar,
i have configured the partner profile for the LOGICAL SYSTEM that i hav created along with the message control deatils in msg ctrl tab( which i think should not really matter) as i have already created a distrib. model for my log. sys and attached my msg typ to that.
when i debug the flow ( rsnast00-rsnasted-ale_processing-idoc_output_ordrsp) i think the error is somewhere in the call function tede1-routid( idoc_output_ordrsp) in the new_dyn_perform subroutine.
but that FM is holding good for other ORDRSP idocs.i am really unable to understand where the error actually is.
thanks

Idoc not created for a particular sales order

Hi,
For a particular sales order , idoc is not created .
The idoc has to be generated when we create a sales order ,
but for a particular sales order , the idoc is not generated when the sales order is created. The program is assigned in
nace for output type zd00.
RSNASTED is the program which triggers the idoc and FM: IDOC_OUTPUT_ORDRSP.
How to debug and see why the idoc is not generated,
i had kept break point in idoc_output_ordrsp function module
and program rsnasted, but my control does not
reaches this point.
can anyone help me in this issue.
Thanks and regards,
A. thirumaran.
Edited by: thirumaran a on Jul 22, 2008 1:35 PM

Hi,
Could you please check if the output is processed or not, whether in the output type what all conditions you have maintained e.g send immediately.
Reward me point if you find this helpful.
regds.......
Sumit

To recover data of two tables ORACLE and to create IDOC Finsta

Hello expert:
I have the following scene:
SAPR/3 <----
 XI <----
ORACLE
(To process Idoc) (CREAR IDOC PAYEXT) (Table: Header and Table: Detail).
i need to recover the information of ORACLE of two tables (Headed and it details), to take the data to XI
and to create the IDOC(PAYEXT), finally to give it to SAPR/3.
my problems are two:
Not like recovering the information of the two tables at the same time related by the field key.
In addition I need to create in IDOC (Finsta) to SAPR/3.
I hope that they can help me
thanks
Raúl.

Help me please!
Example one:
select H.ID_TRANSAC H.FEC_PAGO H.HOR_PAGO D.NUM_REFERENCIA D.IMPTE_PAGO
FROM PPQ_PAGO_CENTRA_H AS H INNER JOIN PPQ_PAGO_CENTRA_d AS D ON H.ID_TRANSAC = D.ID_TRANSAC where H.ID_TRANSAC = '5686496'
Example two:
SELECT PPQ_PAGO_CENTRA_H.ID_TRANSAC PPQ_PAGO_CENTRA_H.FEC_PAGO PPQ_PAGO_CENTRA_D.ID_TRANSAC PPQ_PAGO_CENTRA_D.NUM_REFERENCIA
FROM PPQ_PAGO_CENTRA_H INNER JOIN PPQ_PAGO_CENTRA_d ON PPQ_PAGO_CENTRA_H.ID_TRANSAC = PPQ_PAGO_CENTRA_D.ID_TRANSAC
WHERE PPQ_PAGO_CENTRA_H.ID_TRANSAC = '5686496'
It gives errors me of the two forms. You help me with an example of the Join?

IDocs not created in file to IDoc scenario

Hi all
I am trying this file to IDoc scenario.
File picked up successfully and sent to R/3 BackendBut Idoc is not postedthe status records
In /n we05 in R/3 Backend shows that EDI: Partner profile inbound not available
I created/tested all basics like RFC dest, port etc.
File service that I am using is a business service hence I am specifying a Logical system name in
Adapter specific Identifiers of the file service.
I disabled EDI_DC40 control tag record as IDoc adapter
takes care of it.
So at first I tried the configuration of IDoc comm. Channel by checking the Apply control record values from payload
But SXMB monitor gave an error regarding this control record tagI guess as we have disabled it so there wont be any values
for control record in payload (correct me if I am wrong).
So I unchecked the checkbox Apply control record values from payload and monitor showed up as successfully processed.
But in the backend I am getting this error regarding partner profile.
I also tried to use an existing profile (LS type) by modifying its inbound parameters to accept CREMAS Idoc.
But the error is as persistent as me
Pls help
Sudhir

Hi
Sender --> LEGACY, maintained in SLD (Logical system).
Receiver--> ENI maintained in SLD with logical sys name M700.
Partner Profile LEGACY maintained in R3.
Following is the IDocOutbound in SXMB monitor in XI.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>100</SAP:MANDT>
<SAP:DOCREL>640</SAP:DOCREL>
<SAP:DOCNUM>0000000000001013</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>CREMAS03</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>CREMAS</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPAXI</SAP:SNDPOR>
<SAP:SNDPRN>LEGACY</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPENI</SAP:RCVPOR>
<SAP:RCVPRN>M700</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL />
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS />
<SAP:OUTMOD />
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>0000-00-00</SAP:CREDAT>
<SAP:CRETIM>00:00:00</SAP:CRETIM>
<SAP:ARCKEY>DF57A2C0532811D9AD84000F206A031B</SAP:ARCKEY>
</SAP:IDocOutbound>
Control record of IDoc in R3
Tab: Typeinfo
 Basic type-->CREMAS03
 Message Type-->CREMAS
Tab: Partner
 Recipient
 Port -->SAPENI
 Partner Number--> M700
 Partner Type-->LS
 Sender
 Port -->SAPAXI
 Partner Number--> LEGACY
 Partner Type-->LS
Pls help
Regards
Sudhir

Output type not created for outbound delivery while using SHMNT05 idoc type

Hi Experts,
Please help me to solve the below issue.
Problem:- I want to to generate an IDOC(using type SHPMNT06) once the PGI is done for an outbound delivery.
Already it is working fine when used DESADV.DESADV01 or DESADV.DELVRY07. But now the output type is not getting created when used SHMNT.SHPMNT06. I have created a separate output type ZPJ7 just as a mirror copy of the earlier output type(ZPJ6) used for DESADV.DELVRY07.
Question:- Is it possible to use idoc SHPMNT06 instead for DESADV01 or DELVRY07? If yes then what are steps to be followed?
The reason why SHPMNT06 idoc is planned:- We have a scenario to send outbound delivery to 3rd party system via XI. If the outbound delivery is for National(Not for Export) and PGI is completed then send the idoc straight forward to XI otherwise DO NOT generate the idoc, but just create the delivery. Collect all the deliveries in a transport and send it in a shipment. The shipment details can be sent using SHPMNT idoc. Now from XI perspective, if we can utlitze the same SHPMNT idoc for the National delivery(1st case) then perhaps this will require less effort. Hence shipment idoc is required to be generated when the delivery is created and PGI is done.
Also it would be great if you can advice some better way to solve above mentioned scenario.
Many Thanks,
Sanjay

There could be several reasons. Go to the document and in the extras-output check output determination analysis in the processing log.
If the output has been created successfully then you need to see your printer determination. Ask basis to check it up. If the problem is that even the print preview is not coming. Check your communication in the output analysis and ensure LOCL is selected. Any other printer will need to be configured.
If thats done already then check whether you have maintianed the condition record.
If that too is done then check whether your output type has been assigned to the output procedure and that the output type is listed in the procedure.
regds
Jude

IDOC_INBOUND_ASYNCHRONOUS FM not creating new IDOC?

Hi,
IDOC_INBOUND_ASYNCHRONOUS function module is not creating new IDOC in SAP.
I configured all related functions against message type and idoc type.
Please let me know the issue.
I am processing old IDOC (created from non sap system) through BD87 and using custom function module. I called IDOC_INBOUND_ASYNCHRONOUS in custom function module.
Chandra

Hello,
Aren't you getting any error messages ? You may check by creating watch points on the message id and / or number .
Thanks

Mapping Issue: Target IDoc structure not getting created properly

Hi Experts,
I am stuck with a strange problem in my mapping. It is a M:N scenario mapping where we have multiple IDocs in source as well as in target.
For example, in source Queue-1 I am getting values as [SUPPRESS, true, true, true, true] and in the in source Queue-2 I am getting the values as [1,2,3,4,5]. I used MapWithDefault function to match the number of values in both the queues but in the target IDoc the node (say TMPN) is created only 4 times because of the condition put at the target node. So, the target node should have values as [1,2,3,4] but it gets values as [2,3,4,5] because the first target TMPN node is not created in the first target IDoc. I can provide you with the skeleton of the map. Hope this will give you a fair idea. Let me know if you require more details.
1. Target Structure:
    IDoc - No TMPN Node
    IDoc - 1 TMPN Node
    IDoc - 2 TMPN nodes
    IDoc - 1 TMPN node
Condition put on target TMPN_Node ---> (created only 4 times due to condition)
2. Mapping Skeleton:
Values coming from Q1 (SUPPRESS, true, true, true, true) --->
                                                                                \===>FORMATBYEXAMPLE+SPLITBYVALUE==> TMPN-F0 [2]
                                                                                /                                                                              TMPN-F0 [3]
Values coming from Q2 (1,2,3,4,5) -
>                                                                               TMPN-F0 [4]
                                                                                TMPN-F0 [5]
Where F0 is the field which is created when TMPN Node is created. So, if TMPN gets created 6 times, the F0 gets created 6 times.
Please let me know if there is an alternative to this problem. How can I have values as [1,2,3,4] in field F0 instead of [2,3,4,5]

hi,
i got the email.
as i can see your mapping seams to be rigth, but there is sometrhing i dont get. in a previuos post you said:
I am stuck with a strange problem in my mapping. It is a M:N scenario mapping where we have multiple IDocs in source as well as in target.
For example, in source Queue-1 I am getting values as SUPPRESS, true, true, true, true and in the in source Queue-2 I am getting the values as 1,2,3,4,5. I used MapWithDefault function to match the number of values in both the queues but in the target IDoc the node (say TMPN) is created only 4 times because of the condition put at the target node. So, the target node should have values as 1,2,3,4 but it gets values as 2,3,4,5 because the first target TMPN node is not created in the first target IDoc. I can provide you with the skeleton of the map. Hope this will give you a fair idea. Let me know if you require more details.
1. Target Structure:
IDoc - No TMPN Node
IDoc - 1 TMPN Node
IDoc - 2 TMPN nodes
IDoc - 1 TMPN node
lets asume you define as default value "1"
now, the result of the formatByExample taking the example you sent to me is:
1,T1,T2,T3,T4 without context change. and the result of the function splitByValue should be what you are specting.
but its something that is not clear still,
could you post the result of the mapWithDefault? i think your problem is there.
Rgds
RP-.

Inbound IDOC not creating B007 relationship (HRP1001)

Hi,
I have an inbound IDOC containing object type S (Position) and object type C (Job), plus various relationships including A007 and B007 between the Job and the Position.
All of the relationships get created except the B007 i.e. the Position cannot link to the Job? This is happening for some jobs only....
We checked with all the possible testcases but could not find the clue....
Kindly let me know if anyone have answer ??
Thanks in Advance.

Glen,
Thanks for your Quick response.
Firstly I would like to tell you that the relationship is not created for only couple of Jobs which were existed in the system. But if I do same by creating new records(jobs) its flowing perfectly.
It's giving neither error message nor the Subsegment for this created Object.

MATMAS IDOC not creating required views

Hi
We have a scenario where an external system is sending material master data to ECC via PI. The msg type used is MATMAS03. The data gets processed successfully in ECC but does not create the basic data views. The inbound idoc has many fields which belong to basic data views, yet the views that have similar fields other than basic data get created. We have checked the configuration for screen sequencing (Industry standard sequence) and analysed the function module used for inbound processing of idocs. We did not find anything wrong with them. We see that the VPSTA and PSTAT maintenance fields get populated with all other views other than Basic data 1 and 2. This is automatically handled by SAP standard logic.
Does anybody have any idea what could be causing this? Any troubleshooting tips will help.
Thanks
Arvind

do you have a valid warehouse number and data for your warehouse in the IDOC?

For the new delivery type created the Idoc is not getting triggered

Hi All,
I am facing the following problem:
For every outbound delivery getting created we have an Idoc which creates the file(sending the outbound delivery details), this file is sent to a system where the picking & packing of the goods happen. This process seems to be working fine for all the existing delivery types, but now we created a new delivery type for which the Idoc is not getting triggered.
Would like to understand what setting are we missing because of which the Idoc is not getting created for the new delivery type.
The Idoc being used is: DESADV01
Message type :DESADV
Thanks,
Geeta

I believe your existing idocs are created through a output type on the delivery ? if yes, probably you need to configure an existing output type / create a new output type for your new delivery type...

F9N7- IDOC FINSTA not created

Similar Messages

Maybe you are looking for