IDOC is in Yellow state

Hi All,
By using the custom program, I am creating the IDOC and after that I am running the program "RSEOUT00".But still IDOC is in Yellow state.
If run the IDOC in WE17 Transaction code, IDOC state is getting turned into Green state.
Could you please tell me what could be the problem.Why it is Yellow state.

Hi,
We faced the same problem .
Chek your Coneection string in SM59. Reset IP address with host name and system number and try again.
Check response time in SM59.
Check SM58 if any error is there in RFC after idoc processing.
Salil ...

Similar Messages

IDOC in yellow state after MASTER_IDOC_DISTRIBUTE

Hello,
I am sending idocs using MASTER_IDOC_Distribute to the target. In the partner profile, I have checked process idocs immediately.
After the function call, there is commit work command.
I like to process idocs immediately.
Most of the time the idocs are in yellow state, and require BD87 to process idocs. I checked several tips in SDN and unable to resolve it.
Thank you for the help
Regards
William

Hi William,
The below links might be helpful for your problem:
[Call of master_idoc_distribute|http://help.sap.com/saphelp_nw04/helpdata/en/78/21783151ce11d189570000e829fbbd/frameset.htm]
[Re: Use of MASTER_IDOC_DISTRIBUTE|Re: Use of MASTER_IDOC_DISTRIBUTE]
Regards
Bhanu
Intelligroup.
Edited by: Bhanu Tiruveedula on May 13, 2008 8:10 PM

Init Load showing in yellow state.

Hi all,
I am trying to do init for SRM data source to ODS object.
The init load is showing yellow state (0-0 records).
There is no data available in SRM related to this data source.
Can anyone please tell me why it is in yellow state instead of green.
Thanks
S VR.

Hi S VR,
In the monitor screen go to the Status Tab > click on the lights next to Total > Make it Red and save > the system will prompt a couple of messages, say Yes to them. Then you can Manual Update. Once all packages are done (green), then again Status tab > click onthe lights next to Total > Delete Statsu; back to request status > Save. The request should now be green.
else
try repair full request option it can help you..
Hope this helps...
Assign points if helpful...
Regards,
NR
Edited by: N R Pradeep Reddy on Apr 14, 2008 6:14 AM

Request in Yellow State in Delta update cube.

Dear Exprts,
In request , no. of transfered record is 73260 & added record in cube 73212 with yellow status. Everything O.K. but in Data package 2 in update rule it has tranfered only 16247 out of 16295. ( this is same diffrence of number of records as in cube ) .
PSA request is also in yellow state.
Regards,
Anand Mehrotra.

Dear experts,
Thanks for reply.
In R/3 & BW , it showing status job is finished . But PSA request is also yellow state.
In transfer rule ( Data package 2 ) no of tranfered record is equal to added . But Update rule it is different green status.
how to find out these records in update rule.
Regards,
Anand Mehrotra.

PSA Request struck in yellow state if no data is available

If there is no data available in the source system then the PSA reuest in the Datasource is not updated as sucess rather it is struck in yellow state.
However, if there is data available then there is no issue.
We are running a delta load through a Process chain and daily we have to manually set the satus to sucess for the chain to continue its execution.
Any help would be appreciated

Time out time(TOT)
This settings are useful when we have huge data and load will take more time. in general default time out time maintained some number(ex 7hours).
when that time was crossed we get time out time error for info pack. in that case we need to increase the wait time for info pack.
Treatment for warning(TFW) - if we receive any warning during the load in default request will be red. in generally warnings are allowed. once you check what is the warning, after that accordingly warning message you can make request to green.

Datasource 0UC_SWTMSGDATA - request remains in yellow state

hi all,
we are using the datasource 0UC_SWTMSGDATA to extract message data for the switch documents.
every time we scheduled the infopackage to load data into sap bi, the datasource extracts all data records to the bi.
but at the end, when all records arrived at bi, the request remains in yellow state.
do you have the same problem? what's the reason?
we are already using the datasource 0UC_SWTDOC, it works fine.
kind regards,
phil
Edited by: Philipp Südfeld on Jul 8, 2011 4:49 PM

Hi,
You have to check the job status in SM37 in R/3 system. If it shows "Active mode", then you will be getting Yellow color in BW. You may have to wait till the job gets finished in R/3.
Sometimes, transferring I-Docs take time.
Regards,
Suman

Transfer rules yellow state

Hi Exterts,
i have done the BC installation of 0PM_C03
now we have to make it adaptable to our system by creating ZC objects
so i have created ZC objects
now transfer rules are in yellow state even though i have activated it
i saw the mapping.
some infoobjects and some field are not mapped in transfer rules
but i could see that all the objects that are present in 0PM_C03 are mapped in transfer rules and also all objects are mapped in update rules.
now what i have to do to make transfer rules as green
Please Advise ,
Thanks in Advance.
Nitya

HI
try this,
1.check the all dependent objects are in active version or not?
2. are you giving the right source system name, technical name also check if any source system dependent fields your using and trying to club with different sourcesystem in transfer structure?
3. Transfer Rule with YELLOW status signifies that there are fields/InfoObjects which are yet to be mapped.If all the Fields/InfoObejcts are mapped then the status would be GREEN.
check the link
Edited by: Srikanth.T on Nov 3, 2011 9:54 AM

Bapi or idoc for electronic bank statement

may you please assist me on which bapi and or idocto use for elctronic bank statement idocand guide me on how to implement the two

Hello,
If you want to use Idoc for electronic bank statement then idoc type should be :FINSTA01 & message type is FINSTA.
For additional information check the following link: http://help.sap.com/saphelp_nw04/helpdata/en/e4/52ec78bfff11d295f400a0c9426c73/content.htm.
Hope this is what you were looking for .
Thanks.

TR-EBS SwiftMT940 mapping to an IDOC message FINSTA01 - Bank Statements

For Treasury, we are going to move to the PI platform. We are currently using EDI.
We start the process by requesting Citibank(GXS operations team) to put a sample file into the outbound mailbox to let our company pick up. The output of the file will be XML.
We will them map and create an IDOC with the FINSTA message.
However, we are only beginning the IDOC mapping process.
Does anyone have a sample crosswalk which will allow us to see how the SwiftMT940 from Citibank can be mapped to an SAP Idoc?
If so, may we see how you mapped the segments?
Also, how do you test the loading of the IDOC created? with the RFEBKA00 program?
Please advise.

Hello,
I am really not sure how you map to IDOC.
But, the following information may be useful to you.
Hello, You can configure the electronic bank statement at the following path: IMG => Financial Accounting => Bank Accounting => Business Transactions => Payment Transactions => Electronic Bank Statement => Make Global Settings for Electronic Bank Statement. All the settings will be done at this path only. 1. Create Account Symbols 2. Assign Accounts to Account Symbols 3. Create keys for posting rules 4. Define posting rules 5. Create transaction type Assign external transaction types to posting rules 6. Assign bank accounts to transaction types. There are different programs to upload electronic bank statement. FF.5 or FF_5. I think your case Multicash format you are using. You need have three files in FF.5 and two files in FF_5 You can prepare a Z program in order to truncate the electronic bank statement into two or three part files and save them on the application server. 1. Take all the external codes list from bank. 2. Take any available documentation from the Bank describing the relevance of the external codes. 3. Make sure that your Chart of Accounts (Bank Accounts) last digits logic is appropriate to meet the requirements. 4. Based on this decide the Account Symbols that are required to be created. 5. Make sure that the masking rules are configured properly. 6. Decide the posting rules that needs to be created. 7. Link up your external symbols provided by the bank with Posting rules and give proper algorithms for posting and clearing logic. 6. Concentrate on the posting areas to be posted while uploading the bank statement. Further explanation would help you to understand the functionality when uploaded the electronic bank statement. Main purpose of uploading the bank statement into SAP is to make your Bank Main Account and physical bank statement balance in sync. You do not have any traditional Bank Reconciliation Statement (BRS) report in SAP. SAP is normally you maintain bank main account and bank sub account. Whenever you make a payment through F-53 or F-58 or F110, the entry would be: Vendor Account Dr To Bank Sub Account The ending digits of the sub-account would be important in configuring the masking rule. Based on this masking rule when you upload the bank statement the entry the system would pass is: Bank Sub Account Dr To Bank Main Account It depends on the configuration, either the sub account will be cleared by the system automatically or you need to run F.13 to clear the sub accounts. At the time of receipts, you have different accounting entries unlike payments. It needs to post to two posting areas. 1. GL Accounting 2. Sub-Ledger Accounting The entries would system itself pass is: Bank Main Account Dr To Bank Sub Account Bank Sub Account Dr To Cutomer account. Clearing logic mentioned for your posting rules and the alogrithm used for your external bank symbols will also play pivotal role in clearing the accounts. Ideally you will use FF67 / FF.5 / FF_5 for uploading manual or electronic bank statement FEBA / FEBA_BANK_STATEMENT is used for furthe rprocessing. GO THROUGH SAP NOTE 48854 Please go through SAP Note. 48854. You will get an idea regarding the functionality of the algorithms. Though this note is in relevant to GB specific, you will find this very useful. description follows below regarding the normal procedure for maintaining table T028G. Due to the different bank codes and posting rules, pre-Customizing is not possible at this point. The following processing types are available - unless stated otherwise, you should use the interpretation algorithm: '000 - No interpretation' in each case. 1. '00': There is no processing. The entry line is ignored. 2. '01': A validation is made whether an entry exists for the transferred check number in the check table (PAYR). The check number and payment document number are transferred for further processing. Interpretation algorithm: outgoing check processing '011'-'013'; the update in the check file is via the interpretation algorithm. 3. '02': Transfer of the ending balance to the electronic bank statement 4. '03': Transfer of the opening balance to the electronic bank statement 5. '04': Clearing via the allocation number which is delivered with the bank statement. No interpretation algorithm. 6. '05': Clearing of BACS payments or BACS bank collection. The reference text field is first read to ascertain whether it involves payments initiated by users or bank collection via BACS. Providing it does involve a cash transaction initiated by the user, the payment document numbers concerned are determined via the reference number and transferred as a reference to further processing. Interpretation algorithm: '000 - No interpretation' or '019 - Reference number DME'. Note To differentiate between the two procedures in table T028G, you have to maintain two separate entries. Example: the bank uses bank code '62' for cash receipts and for BACS bank collection. Ext. Transaction +/- sign Posting rule Int. Algorithm Processing type 62 + GB62 001 5 62 SAPBACS + GB63 000 5 7. '06': Bank costs or interest revenues Recommended interpretation algorithm: '000 - No interpretation' 8. '07': Total amount of cash disbursements 9. '08': Total amount of cash receipts 10. '09': Items not paid Recommended interpretation algorithm: '000 - No interpretation' Regards, Ravi

IDOC for Customer Account Statement

Hi All,
I have a requirement that the Customer Statement should be sent thru and IDOC for some specific task. We are using the F.27 to print the Customer Account Statement. In the process of finding the IDOC for the same, we found FINSTA01 and Message type FINSTA will suit the requirements. Now the issue is, when i use F.27, it generates the SPOOL and starts priniting the same, insetad i need the same to initiate the IDOC. I mean the communication method to be IDOC instead of the Physical Print. Can anyone help me on how to do this? also please through some light on the things needs to be done if anyone of has come across such requirement.
Thanks in Advance.
Regards
Nambi

Hi Thiruchudar,
There are some setup you need to do. If you're not technically well grounded, i would suggest you get an ABAPer to do this for you. Basically, the following are what you need to do:
1. Create the Partner Profile for your Customer using transaction code WE20. Click on the create icon and enter Partner type KU (Customer) and enter the Customer Number.
2. Next, add an Outbound Message Type FINSTA by clicking on the green + icon under the outbound parameters. Complete all the other mandatory fields as appropriate. Save your Entries.
3. Test your outbound partner profile for your customer by running the customer statement again using transaction code F.27.
Your output control would have been created with the medium EDI.
4. Use transaction code WE05 to display the iDocs that would have been created.
Note: You still have to set up the communication between your system and that of your Customer to allow for EDI transmission.
I hope the above helps.
Do not forget to award the points please.
Thanks and Regards,
Jacob

Load step in Yellow state even after completion

Hi people:
I have a situation here with aprocess chain.
When the process chain is triggered,there is a load step which stays
in yellow even after the load completes. We tried to push the step
forward,but the chain wont progress. So,we had to do the rest of the
steps in the process chain manually.
Why does this hangover step happens in the process chains?
Can some one give a solution to this situation, so that we don't have
to do the steps manually everytime the chain is struck at the step?
Any inputs are appreciated.
Thank you.

Hi,
Check the status of the Process Variant in RSPCPROCESSLOG table. If the status of the variant is not 'G' then the process will not move to the next step though the loads complete succesfully.
In this case you have to change the status to 'Completed' (G)manually.
This could be done using the Function Module 'RSPC_PROCESS_FINISH'.
Provide the below details in the FM
1) I_LOGIN - Login ID of your process variant (you can find this in RSPCPROCESSLOG table)
2) I_TYPE = CHAIN
3) I_VARIANT = Your Proces Chain variant (Optional)
4) I_INSTANCE = Double click on the object which was struck and click on Backg tab. Copy paste the instance.
4) I_STATE = G.
Hope this would resolve your issue.
Regards,
Anil Pragada

Open Hub third Pary extraction in yellow state forever

Hi,
Would appreciate any assistance in this regard.
Here's the situation:
1 - We have third party open hub extraction setup.
2 - All settings are fine : RFC destination, transformations, Open hub.
3 - Now the issue is that we have a third party system which is data stage and teradata.
4 - Now they trigger a job which in turn starts the PC in BW.
5 - This PC has 2 steps only. The start and the DTP.
6 - This DTP loads data from Info-object attributes to Open hub (basically a table).
7 - The DTP technical status is green but overall status stays yellow.
8 - Now I know that for 3rd party, we have several APIs and here's my understandin:
When the extraction is finished and technical status is green, BW notifies 3rd party through RSB_API_OHS_3RDPARTY_NOTIFY.
Then the 3rd party checks the data through RSB_API_OHS_DEST_READ_DATA.
Then if data is fine, the 3rd party send confirmation through RSB_API_OHS_REQUEST_SETSTATUS and the overall status turns to green.
Now I do not understand what's wrong because all of the above mentioned should complete automatically.
We have other openhubs with same RFC destination and they are completing successfully. Just for the information: We have recently moved to SP 10 on EHP1.
Regards
Debanshu

Were you able to solve this? I am also facing exact same problem.
Regards
Pankaj

Error in Setup Package - yellow state

Hi Expert,
I have a problem when you build a setup package for a PDA.
When creating the PDA and leave in an "initial" and press the button to create setup package, the monitor always shows yellow status. The TX: SMQ2 indicates no queue run.
I have implemented the USE_BULK_INSERTS parameter in DOE CONFIGURATION.
Some idea of the problem?
Thanks.

Hi Kranti,
The container is ESWT, and has all the necessary components:
MCD Name          MCD Version
DB2E_PPC          914
NATIVE_PPC          711001
OCA_RT               711001
PDA_CORE          711001
SKELETON          711001
WDLContainerUI     711001
eSWT_PPC          711001
The Queue Details:
Number of Unread Messages: 3.215
Number of Unread Messages: 11.586.426
To trigger the creation of setup package, the monitor displays in task yellow status, and associate TX:SDOE_SETUP not shows nothing. The device status changes to "Pending for Registration" and you can not re-creating the setup package.
The problem apparently occurs when the Setup Data is more than 5MB, since when is less than this, the setup package is created and appears in TX: SDOE_SETUP
Any ideas because as much Data, the setup is not generated?
Thanks

Unable to manually set the BW request status from hanged yellow state

Hi All,
We were running a BW upload when it failed due to some ABAP dump. The request remained in the status yellow.
We tried to manually set the status to red or green in RSA1--> manage (infoprovider)
This did not allow me to reset the status there.
I searched the SDN and found this blog: http://scn.sap.com/community/data-warehousing/netweaver-bw/blog/2013/10/23/deleting-dtp-requests-when-the-dtp-step-is-hanged
But in our case the table : RSBKREQUEST shows "USTATE" and "TSTATE as "0"(zero). I can reset the status only when it shows 5. So running RSBM_GUI_CHANGE_USTATE in SE37 to reset the status to "0" (zero) is not an option here.
Iam sure others would have come across this situation before. If you could throw some light on how to reset the BW request status to RED or Green so that I can restart the load again.
Your help is really appreciated.
Thanks
Manmath

Hi,
please check the below tables have your DTP request ID.
Note: Be aware the deleting the request form the data base tables
RSBKREQUEST
RSREQDONE,
RSREQICODS,
RSICCONT
Thanks,
Phani.

EP6: jcontrol.exe : yellow state

I installed EP6_SP3, but am unable to apply the SP6 upgrade.
I get an error: apparently due to the J2EE server being in the offline mode.
I have noticed that the jcontrol.exe stays yellow all the time and never goes to green.
Anyone having the same issues?
Any fix for this?
Regards,
Shanker

Just wait for a looooooong time. It takes lot of time to start SDM.
Goto process table and check the status of SDM. If it shows stopeed, wait for some time, starting it does not make any difference as it stops immediately.
Usually it starts after 1hr time on P4 1.7/1 GB RAM. On P4 2.8/2 GB RAM it is starting almost immediately.

IDOC is in Yellow state

Similar Messages

Maybe you are looking for