Narrative:

Normal preflight duties were completed. Upon notification through ACARS that performance weight and balance loading data was available; I tried to load the data into the FMC. Only part of the data would load. Incorrect cruise altitude data loaded; and no temperature data; nor N1 data; nor V speed data; nor flap setting data would load. We attempted to reload it several times. I noticed that the enroute cruise altitude was incorrect; and given that; I looked at the entire flight plan route. We were filed on the with an enroute altitude of FL220. This was all loaded correctly into the FMS; but the first altitude on this STAR at point of zzzzz intersection has a published crossing altitude of FL240 to FL300. I recall that dispatch filed us at FL220 for a cursing altitude; and that is what was entered into the system. Since the minimum crossing altitude on the STAR at zzzzz intersection was FL240 to FL300; the performance weight and balance system would not load or take our cruise data into the FMC. When I deleted the first crossing altitude restriction on the STAR at zzzzz intersection (FL240 to 300) on the legs page; then and only then would the performance weight and balance system load into the FMC. This is not really in accordance with procedures; and not something we normally would know or even be trained to know. Bottom line; if the filed cruising altitude is below any altitude restriction on the field and loaded STAR; performance weight and balance data will not load into the FMC. This performance weight and balance system limitation needs to be examined; addressed; and or corrected; and the information distributed throughout flight ops. I am sure I am not the first one who has stumbled across this; but probably the first one who has written in about it.

Related reports:

Google
 

Original NASA ASRS Text

Title: B737 First Officer reported being unable to load some data into the FMC which was caused by the cruising altitude being below the minimum crossing altitude of one of the arrival fixes.

Narrative: Normal preflight duties were completed. Upon notification through ACARS that performance weight and balance loading data was available; I tried to load the data into the FMC. Only part of the data would load. Incorrect cruise altitude data loaded; and no temperature data; nor N1 data; nor V Speed data; nor flap setting data would load. We attempted to reload it several times. I noticed that the enroute cruise altitude was incorrect; and given that; I looked at the entire flight plan route. We were filed on the with an enroute altitude of FL220. This was all loaded correctly into the FMS; but the first altitude on this STAR at point of ZZZZZ intersection has a published crossing altitude of FL240 to FL300. I recall that Dispatch filed us at FL220 for a cursing altitude; and that is what was entered into the system. Since the minimum crossing altitude on the STAR at ZZZZZ intersection was FL240 to FL300; the performance weight and balance system would not load or take our cruise data into the FMC. When I deleted the first crossing altitude restriction on the STAR at ZZZZZ intersection (FL240 to 300) on the LEGS page; then and only then would the performance weight and balance system load into the FMC. This is not really in accordance with procedures; and not something we normally would know or even be trained to know. Bottom line; if the filed cruising altitude is below any altitude restriction on the field and loaded STAR; performance weight and balance DATA WILL NOT LOAD INTO THE FMC. This performance weight and balance system limitation needs to be examined; addressed; and or corrected; and the information distributed throughout Flight Ops. I am sure I am not the first one who has stumbled across this; but probably the first one who has written in about it.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.