Reply from LCC352 on Aug 2 at 3:38 PM It's probably the last field, DATBI. Note that it has to be EQUAL to the date in BSEG. That's not going to happen often if at all, right? So what's happening is that there are no records that will be correct for that selection. You're not getting an error, you're just not getting data. The only reason why you're getting a KOSTL value is because it's the value being used in the join.
If you have a common end date (DATBI) for all of your cost centers, you can use that literal as part of the equality. I've always set up cost centers to end on 12/31/9999. If you put in a literal like that, you might try '99991231' or some combination thereof, enclosed in quotes. If they all end differently, that's going to be an issue because . . .
since you're using that logical database, you do not get the JOIN button - it's greyed out on the menu path and doesn't show up at all. So you can't swtich to doing the JOIN manually, and just leaving off the last field in the process.
Assuming you don't have a common end date for your cost centers, you have two choices: don't use that logical database, or, use that logical database but code for the selection of the table yourself during the record processing section of the infoset. That will require some ABAP, but not much at all. You would need to set up a field for each field you're using from CSKS, and then in each field, insert code that would pull that value from CSKS and put it into the new field.
- Lou
| | | ---------------Original Message---------------
From: JNBradley
Sent: Thursday, August 02, 2012 11:34 AM
Subject: Logical Database BRM and CSKS
I am building an infoset in SQ02 using Logical Databse BRM, I am trying to connect table CSKS, the Cost center field KOSTL is working, but the data from the KIHNR. When I linked the tables I used the linking the systems gave me. Is there something I am doing wrong?
Thanks, J |
| Reply to this email to post your response. __.____._ |   _.____.__ |
